Techniques for dynamically aggregating a physical downlink shared channel for semi-persistent scheduling

ABSTRACT

Methods, systems, and devices for wireless communications are described that support various configurations that enable repetitions of physical downlink shared channel (PDSCH) transmission according to a semi-persistent scheduling (SPS) configuration. A user equipment (UE) may receive downlink control information (DCI) associated with a PDSCH configuration and an SPS configuration. The UE may determine a number of PDSCH repetitions for a PDSCH transmission (e.g., an SPS PDSCH transmission) based on a rule associated with a priority between time domain resource allocation (TDRA) entries and configured repetition factors in an SPS configuration or a PDSCH configuration. The repetition number may be included in the TDRA entry, and the UE may receive a number of PDSCH repetitions based on a value of the PDSCH repetition number, or one instance of PDSCH may be received in each SPS period.

CROSS REFERENCE

The present Application for Patent claims the benefit of U.S.Provisional Patent Application No. 62/993,562 by KHOSHNEVISAN et al.,entitled “TECHNIQUES FOR DYNAMICALLY AGGREGATING A PHYSICAL DOWNLINKSHARED CHANNEL FOR SEMI-PERSISTENT SCHEDULING,” filed Mar. 23, 2020,assigned to the assignee hereof, and expressly incorporated by referenceherein in its entirety.

FIELD OF TECHNOLOGY

The following relates generally to wireless communications and morespecifically to techniques for dynamically aggregating a physicaldownlink shared channel (PDSCH) for semi-persistent scheduling (SPS).

BACKGROUND

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). Examples of suchmultiple-access systems include fourth generation (4G) systems such asLong Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, orLTE-A Pro systems, and fifth generation (5G) systems which may bereferred to as New Radio (NR) systems. These systems may employtechnologies such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal frequency division multiple access (OFDMA), or discreteFourier transform spread orthogonal frequency division multiplexing(DFT-S-OFDM). A wireless multiple-access communications system mayinclude one or more base stations or one or more network access nodes,each simultaneously supporting communication for multiple communicationdevices, which may be otherwise known as user equipment (UE).

Some wireless systems may support communications that aresemi-statically or semi-persistently configured by a base station. Insuch cases, downlink control information (DCI) may indicate theactivation of a semi-persistent scheduling (SPS) configuration forcommunications on downlink channels. In some cases, however, configuringSPS communications may be complex.

SUMMARY

The described techniques relate to improved methods, systems, devices,and apparatuses that support techniques for dynamically aggregating aphysical downlink shared channel (PDSCH) for semi-persistent scheduling(SPS). Generally, the described techniques provide for determining anumber of repetitions of PDSCH for SPS communications. The number ofPDSCH repetitions may be based on a repetition number indicated bydownlink control information (DCI) or may be based on one or moresemi-static configurations. In some examples, a user equipment (UE) mayreceive, via radio resource control (RRC) signaling, an indication of anSPS configuration (e.g., from a set of SPS configurations) and a PDSCHconfiguration. The UE may receive DCI associated with the SPSconfiguration (e.g., DCI that activates PDSCH transmissions for the SPSconfiguration or DCI that schedules one or more retransmissions of anSPS PDSCH). An expected number of instances of an SPS PDSCH (e.g.,within an SPS periodicity given by the SPS configuration) may bedetermined using a rule that is based on a priority between variousconfigurations, where the rule may be used to identify whichconfiguration may be used to identify a number of PDSCH repetitions. Forexample, the number of PDSCH repetitions may be dynamically indicatedusing a time domain resource allocation (TDRA) field within DCI, where aTDRA entry in the TDRA field may indicate a repetition number that isused for the number of PDSCH repetitions. Here, the TDRA entry may befrom a TDRA table including at least one TDRA entry that includes therepetition number. In some examples, a first aggregation factor may beconfigured by the PDSCH configuration and/or a second aggregation factormay be configured by the SPS configuration. In some cases (such as whenthe TDRA entry does not include the repetition number), one or both ofthe first aggregation factor or the second aggregation factor (ifconfigured) may be used for determining the SPS PDSCH repetitions. Inother cases, it may be determined that a single instance of PDSCH may betransmitted based on the various configurations, for example, asdetermined by the rule.

In some examples, a number of PDSCH repetitions for SPS PDSCH may bedetermined based on a configured repetition scheme for PDSCH and anumber of configured transmission configuration indicator (TCI) states.When multiple TCI states are indicated (e.g., by DCI), then multiple(e.g., two or more) repetitions of the PDSCH may be included in a sameslot in respective SPS periods. In some other cases, each SPS PDSCH maybe repeated multiple (e.g., two or more) times per slot across a numberof consecutive slots. Additionally or alternatively, the repetitionscheme may be configured for a particular SPS configuration, and therepetitions of the PDSCH for SPS (when activated) may be based on theconfiguration-specific repetition scheme (e.g., as indicated by the SPSconfiguration, the PDSCH configuration, or both).

A method of wireless communication at a UE is described. The method mayinclude receiving a PDSCH configuration and a SPS configuration from aset of one or more SPS configurations, receiving DCI associated with aPDSCH transmission for the SPS configuration, determining, based on arule, a repetition number for a number of expected instances of thePDSCH transmission, where the rule is based on a priority between a TDRAentry indicated by the DCI and at least one of the PDSCH configurationor the SPS configuration, and receiving, within each SPS time period ofa set of SPS time periods, one or more instances of the PDSCHtransmission in accordance with the repetition number.

An apparatus for wireless communication at a UE is described. Theapparatus may include a processor, memory coupled with the processor,and instructions stored in the memory. The instructions may beexecutable by the processor to cause the apparatus to receive a PDSCHconfiguration and a SPS configuration from a set of one or more SPSconfigurations, receive DCI associated with a PDSCH transmission for theSPS configuration, determine, based on a rule, a repetition number for anumber of expected instances of the PDSCH transmission, where the ruleis based on a priority between a TDRA entry indicated by the DCI and atleast one of the PDSCH configuration or the SPS configuration, andreceive, within each SPS time period of a set of SPS time periods, oneor more instances of the PDSCH transmission in accordance with therepetition number.

Another apparatus for wireless communication at a UE is described. Theapparatus may include means for receiving a PDSCH configuration and aSPS configuration from a set of one or more SPS configurations,receiving DCI associated with a PDSCH transmission for the SPSconfiguration, determining, based on a rule, a repetition number for anumber of expected instances of the PDSCH transmission, where the ruleis based on a priority between a TDRA entry indicated by the DCI and atleast one of the PDSCH configuration or the SPS configuration, andreceiving, within each SPS time period of a set of SPS time periods, oneor more instances of the PDSCH transmission in accordance with therepetition number.

A non-transitory computer-readable medium storing code for wirelesscommunication at a UE is described. The code may include instructionsexecutable by a processor to receive a PDSCH configuration and a SPSconfiguration from a set of one or more SPS configurations, receive DCIassociated with a PDSCH transmission for the SPS configuration,determine, based on a rule, a repetition number for a number of expectedinstances of the PDSCH transmission, where the rule is based on apriority between a TDRA entry indicated by the DCI and at least one ofthe PDSCH configuration or the SPS configuration, and receive, withineach SPS time period of a set of SPS time periods, one or more instancesof the PDSCH transmission in accordance with the repetition number.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may further include operations, features,means, or instructions for determining that the PDSCH configurationexcludes a configuration of a first aggregation factor or the SPSconfiguration excludes a configuration of a second aggregation factor,or a combination thereof.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the TDRA entry indicated by the DCIincludes the repetition number, and identifying a number of repetitionsof the PDSCH transmission based at least in part on a value of therepetition number, where two or more instances of the PDSCH transmissionmay be received based on the identified number of repetitions.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the number of repetitions ofthe PDSCH transmission may be within a time period that may be less thanor equal to the SPS time period.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the TDRA entry indicated by the DCIexcludes the repetition number, and determining that the number ofexpected instances of the PDSCH transmission may be equal to one basedon the TDRA entry excluding the repetition number, where a singleinstance of the PDSCH transmission may be received based on the numberof expected instances.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the TDRA entry indicated by the DCIexcludes the repetition number, identifying, based on the TDRA entryexcluding the repetition number, a configuration of a first aggregationfactor from the SPS configuration, and identifying a number ofrepetitions of the PDSCH transmission corresponding to a value of thefirst aggregation factor, where two or more instances of the PDSCHtransmission may be received based on the identified number ofrepetitions.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the TDRA entry indicated by the DCIexcludes the repetition number, determining, based on the TDRA entryexcluding the repetition number, that the SPS configuration excludes aconfiguration of a first aggregation factor, identifying, based on theSPS configuration excluding the configuration of the first aggregationfactor, a configuration of a second aggregation factor from the PDSCHconfiguration, and identifying a number of repetitions of the PDSCHtransmission corresponding to a value of the second aggregation factor,where two or more instances of the PDSCH transmission may be receivedbased on the identified number of repetitions.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the TDRA entry indicated by the DCIexcludes the repetition number, determining, based on the TDRA entryexcluding the repetition number, that the SPS configuration excludes aconfiguration of a first aggregation factor, determining, based on theSPS configuration excluding the configuration of the first aggregationfactor, that the PDSCH configuration excludes a configuration of asecond aggregation factor, and determining that the number of expectedinstances of the PDSCH transmission may be equal to one based on theTDRA entry excluding the repetition number, the SPS configurationexcluding the configuration of the first aggregation factor, and thePDSCH configuration excluding the configuration of the secondaggregation factor, where a single instance of the PDSCH transmissionmay be received based on the number of expected instances.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying, from theSPS configuration, a configuration of a first aggregation factor, andidentifying a number of repetitions of the PDSCH transmissioncorresponding to a value of the first aggregation factor, where two ormore instances of the PDSCH transmission may be received based on theidentified number of repetitions.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining that theSPS configuration excludes a configuration of a first aggregationfactor, identifying, based on the SPS configuration excluding theconfiguration of the first aggregation factor, a configuration of asecond aggregation factor from the PDSCH configuration, and identifyinga number of repetitions of the PDSCH transmission corresponding to avalue of the second aggregation factor, where two or more instances ofthe PDSCH transmission may be received based on the identified number ofrepetitions.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining that theSPS configuration excludes a configuration of a first aggregationfactor, determining, based on the SPS configuration excluding theconfiguration of the first aggregation factor, that the PDSCHconfiguration excludes a configuration of a second aggregation factor,and determining that the number of expected instances of the PDSCHtransmission may be equal to one based on the SPS configurationexcluding the configuration of the first aggregation factor and thePDSCH configuration excluding the configuration of the secondaggregation factor, where a single instance of the PDSCH transmissionmay be received based on the number of expected instances.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying, from thePDSCH configuration, a configuration of a first aggregation factor, andidentifying a number of repetitions of the PDSCH transmissioncorresponding to a value of the first aggregation factor, where two ormore instances of the PDSCH transmission may be received based on theidentified number of repetitions.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining that thenumber of expected instances of the PDSCH transmission may be equal toone based on the PDSCH configuration excluding a configuration of thefirst aggregation factor, where a single instance of the PDSCHtransmission may be received based on the number of expected instances.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the TDRA entry may be from aTDRA table that includes a set of TDRA entries, and where at least oneTDRA entry of the set of TDRA entries includes the repetition number.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving aconfiguration of the TDRA table via RRC signaling.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the repetition number may beindicated by at least one column of the TDRA table.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the DCI may have a cyclicredundancy check that may be scrambled by a configured scheduling radionetwork temporary identifier, the DCI including a new data indicatorequal to zero, and where the DCI activates the SPS configuration.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the DCI may have a cyclicredundancy check that may be scrambled by a configured scheduling radionetwork temporary identifier, the DCI including a new data indicatorequal to one, and where the PDSCH transmission includes a retransmissionof semi-persistently scheduled PDSCH scheduled by the DCI.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the one or more instances ofthe PDSCH transmission may be received in a different slot time periodof a set of consecutive slot time periods.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the DCI may have a DCI format1_1.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the DCI may have a DCI format1_2.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the PDSCH configuration andthe SPS configuration may be received via RRC signaling.

A method of wireless communication at a UE is described. The method mayinclude receiving a SPS configuration from a set of one or more SPSconfigurations, identifying a repetition scheme configuration, receivingDCI associated with a PDSCH transmission for the SPS configuration,identifying, within the DCI, an indication of a set of transmissionconfiguration indicator states, and receiving one or more repetitions ofthe PDSCH transmission based on the repetition scheme configuration, orthe set of transmission configuration indicator states, or a combinationthereof.

An apparatus for wireless communication at a UE is described. Theapparatus may include a processor, memory coupled with the processor,and instructions stored in the memory. The instructions may beexecutable by the processor to cause the apparatus to receive a SPSconfiguration from a set of one or more SPS configurations, identify arepetition scheme configuration, receive DCI associated with a PDSCHtransmission for the SPS configuration, identify, within the DCI, anindication of a set of transmission configuration indicator states, andreceive one or more repetitions of the PDSCH transmission based on therepetition scheme configuration, or the set of transmissionconfiguration indicator states, or a combination thereof.

Another apparatus for wireless communication at a UE is described. Theapparatus may include means for receiving a SPS configuration from a setof one or more SPS configurations, identifying a repetition schemeconfiguration, receiving DCI associated with a PDSCH transmission forthe SPS configuration, identifying, within the DCI, an indication of aset of transmission configuration indicator states, and receiving one ormore repetitions of the PDSCH transmission based on the repetitionscheme configuration, or the set of transmission configuration indicatorstates, or a combination thereof.

A non-transitory computer-readable medium storing code for wirelesscommunication at a UE is described. The code may include instructionsexecutable by a processor to receive a SPS configuration from a set ofone or more SPS configurations, identify a repetition schemeconfiguration, receive DCI associated with a PDSCH transmission for theSPS configuration, identify, within the DCI, an indication of a set oftransmission configuration indicator states, and receive one or morerepetitions of the PDSCH transmission based on the repetition schemeconfiguration, or the set of transmission configuration indicatorstates, or a combination thereof.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying a number ofthe one or more repetitions of a PDSCH based on the PDSCH excluding aconfiguration of a first aggregation factor or the semi-persistentscheduling configuration excluding a configuration of a secondaggregation factor, or a combination thereof.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, receiving the one or morerepetitions of the PDSCH transmission may include operations, features,means, or instructions for receiving the one or more repetitions of thePDSCH transmission within a same slot time period, the slot time periodoccurring within each SPS time period of a set of SPS time periods.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, receiving the one or morerepetitions of the PDSCH transmission may include operations, features,means, or instructions for receiving the one or more repetitions of thePDSCH transmission within a set of consecutive slot time periodsoccurring within each SPS time period of a set of SPS time periods, eachslot time period of the set of consecutive slot time periods includingtwo repetitions of the PDSCH transmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying, from theSPS configuration, a configuration of a first aggregation factor, andidentifying a number of the set of consecutive slot time periods thatcorresponds to a value of the first aggregation factor.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving a PDSCHconfiguration, determining that the SPS configuration excludes aconfiguration of a first aggregation factor, identifying, based on theSPS configuration excluding the configuration of the first aggregationfactor, a configuration of a second aggregation factor from the PDSCHconfiguration, and identifying a number of the set of consecutive slottime periods that corresponds to a value of the second aggregationfactor.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, identifying the repetitionscheme configuration may include operations, features, means, orinstructions for identifying the repetition scheme configuration basedon the received SPS configuration.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, identifying the repetitionscheme configuration may include operations, features, means, orinstructions for receiving a PDSCH configuration, and identifying therepetition scheme configuration based on the received PDSCHconfiguration, where the SPS configuration excludes the repetitionscheme configuration.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the set of transmissionconfiguration indicator states includes two transmission configurationindicator states.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the repetition schemeconfiguration may include a first frequency division multiplexingscheme, a second frequency division multiplexing scheme, or a timedivision multiplexing scheme.

A method of wireless communication at a base station is described. Themethod may include transmitting, to a UE, a PDSCH configuration and aSPS configuration from a set of one or more SPS configurations,transmitting, to the UE, DCI associated with a PDSCH transmission forthe SPS configuration, determining, based on a rule, a repetition numberfor a number of expected instances of the PDSCH transmission, where therule is based on a priority between a TDRA entry indicated by the DCIand at least one of the PDSCH configuration or the SPS configuration,and transmitting, within each SPS time period of a set of SPS timeperiods, one or more instances of the PDSCH transmission in accordancewith the repetition number.

An apparatus for wireless communication at a base station is described.The apparatus may include a processor, memory coupled with theprocessor, and instructions stored in the memory. The instructions maybe executable by the processor to cause the apparatus to transmit, to aUE, a PDSCH configuration and a SPS configuration from a set of one ormore SPS configurations, transmit, to the UE, DCI associated with aPDSCH transmission for the SPS configuration, determine, based on arule, a repetition number for a number of expected instances of thePDSCH transmission, where the rule is based on a priority between a TDRAentry indicated by the DCI and at least one of the PDSCH configurationor the SPS configuration, and transmit, within each SPS time period of aset of SPS time periods, one or more instances of the PDSCH transmissionin accordance with the repetition number.

Another apparatus for wireless communication at a base station isdescribed. The apparatus may include means for transmitting, to a UE, aPDSCH configuration and a SPS configuration from a set of one or moreSPS configurations, transmitting, to the UE, DCI associated with a PDSCHtransmission for the SPS configuration, determining, based on a rule, arepetition number for a number of expected instances of the PDSCHtransmission, where the rule is based on a priority between a TDRA entryindicated by the DCI and at least one of the PDSCH configuration or theSPS configuration, and transmitting, within each SPS time period of aset of SPS time periods, one or more instances of the PDSCH transmissionin accordance with the repetition number.

A non-transitory computer-readable medium storing code for wirelesscommunication at a base station is described. The code may includeinstructions executable by a processor to transmit, to a UE, a PDSCHconfiguration and a SPS configuration from a set of one or more SPSconfigurations, transmit, to the UE, DCI associated with a PDSCHtransmission for the SPS configuration, determine, based on a rule, arepetition number for a number of expected instances of the PDSCHtransmission, where the rule is based on a priority between a TDRA entryindicated by the DCI and at least one of the PDSCH configuration or theSPS configuration, and transmit, within each SPS time period of a set ofSPS time periods, one or more instances of the PDSCH transmission inaccordance with the repetition number.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the TDRA entry indicated by the DCIincludes the repetition number, and identifying a number of repetitionsof the PDSCH transmission based at least in part on a value of therepetition number, where two or more instances of the PDSCH transmissionmay be transmitted based on the identified number of repetitions.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the number of repetitions ofthe PDSCH transmission may be within a time period that may be less thanor equal to the SPS time period.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the TDRA entry indicated by the DCIexcludes the repetition number, and determining that the number ofexpected instances of the PDSCH transmission may be equal to one basedon the TDRA entry excluding the repetition number, where a singleinstance of the PDSCH transmission may be transmitted based on thenumber of expected instances.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the TDRA entry indicated by the DCIexcludes the repetition number, where the SPS configuration includes aconfiguration of a first aggregation factor, and identifying a number ofrepetitions of the PDSCH transmission corresponding to a value of thefirst aggregation factor, where two or more instances of the PDSCHtransmission may be transmitted based on the identified number ofrepetitions.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the TDRA entry indicated by the DCIexcludes the repetition number, where the SPS configuration excludes aconfiguration of a first aggregation factor and the PDSCH configurationincludes a configuration of a second aggregation factor, and identifyinga number of repetitions of the PDSCH transmission corresponding to avalue of the second aggregation factor, where two or more instances ofthe PDSCH transmission may be transmitted based on the identified numberof repetitions.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the TDRA entry indicated by the DCIexcludes the repetition number, where the SPS configuration excludes aconfiguration of a first aggregation factor and the PDSCH configurationexcludes a configuration of a second aggregation factor, and determiningthat the number of expected instances of the PDSCH transmission may beequal to one based on the TDRA entry excluding the repetition number,the SPS configuration excluding a configuration of the first aggregationfactor, and the PDSCH configuration excluding a configuration of thesecond aggregation factor, where a single instance of the PDSCHtransmission may be transmitted based on the number of expectedinstances.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for configuring a first aggregation factor as part of theSPS configuration, and identifying a number of repetitions of the PDSCHtransmission corresponding to a value of the first aggregation factor,where two or more instances of the PDSCH transmission may be transmittedbased on the identified number of repetitions.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the SPS configuration excludes aconfiguration of a first aggregation factor, where the PDSCHconfiguration includes a configuration of a second aggregation factor,and identifying a number of repetitions of the PDSCH transmissioncorresponding to a value of the second aggregation factor, where two ormore instances of the PDSCH transmission may be transmitted based on theidentified number of repetitions.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the number of expected instances ofthe PDSCH transmission may be equal to one based on the SPSconfiguration excluding a configuration of a first aggregation factorand the PDSCH configuration excluding a configuration of a secondaggregation factor, where a single instance of the PDSCH transmissionmay be transmitted based on the number of expected instances.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for configuring a first aggregation factor as part of thePDSCH configuration, and identifying a number of repetitions of thePDSCH transmission corresponding to a value of the first aggregationfactor, where two or more instances of the PDSCH transmission may betransmitted based on the identified number of repetitions.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, determining the repetitionnumber based on the rule may include operations, features, means, orinstructions for determining that the number of expected instances ofthe PDSCH transmission may be equal to one based on the PDSCHconfiguration excluding a configuration of a first aggregation factor,where a single instance of the PDSCH transmission may be transmittedbased on the number of expected instances.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the TDRA entry may be anentry from a TDRA table that includes a set of TDRA entries, and whereat least one TDRA entry of the set of TDRA entries includes therepetition number.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the DCI includes a new dataindicator equal to zero, and where the DCI activates the SPSconfiguration.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the DCI includes a new dataindicator equal to one, and where the PDSCH transmission includes aretransmission of semi-persistently scheduled PDSCH scheduled by theDCI.

A method of wireless communication at a base station is described. Themethod may include transmitting, to a UE, a SPS configuration from a setof one or more SPS configurations, configuring a repetition scheme forthe UE, transmitting, to the UE, DCI associated with a PDSCHtransmission for the SPS configuration, configuring, within the DCI, anindication of a set of transmission configuration indicator states, andtransmitting one or more repetitions of the PDSCH transmission to the UEbased on the configured repetition scheme, or the set of transmissionconfiguration indicator states, or a combination thereof.

An apparatus for wireless communication at a base station is described.The apparatus may include a processor, memory coupled with theprocessor, and instructions stored in the memory. The instructions maybe executable by the processor to cause the apparatus to transmit, to aUE, a SPS configuration from a set of one or more SPS configurations,configure a repetition scheme for the UE, transmit, to the UE, DCIassociated with a PDSCH transmission for the SPS configuration,configure, within the DCI, an indication of a set of transmissionconfiguration indicator states, and transmit one or more repetitions ofthe PDSCH transmission to the UE based on the configured repetitionscheme, or the set of transmission configuration indicator states, or acombination thereof.

Another apparatus for wireless communication at a base station isdescribed. The apparatus may include means for transmitting, to a UE, aSPS configuration from a set of one or more SPS configurations,configuring a repetition scheme for the UE, transmitting, to the UE, DCIassociated with a PDSCH transmission for the SPS configuration,configuring, within the DCI, an indication of a set of transmissionconfiguration indicator states, and transmitting one or more repetitionsof the PDSCH transmission to the UE based on the configured repetitionscheme, or the set of transmission configuration indicator states, or acombination thereof.

A non-transitory computer-readable medium storing code for wirelesscommunication at a base station is described. The code may includeinstructions executable by a processor to transmit, to a UE, a SPSconfiguration from a set of one or more SPS configurations, configure arepetition scheme for the UE, transmit, to the UE, DCI associated with aPDSCH transmission for the SPS configuration, configure, within the DCI,an indication of a set of transmission configuration indicator states,and transmit one or more repetitions of the PDSCH transmission to the UEbased on the configured repetition scheme, or the set of transmissionconfiguration indicator states, or a combination thereof.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the one or morerepetitions of the PDSCH transmission may include operations, features,means, or instructions for transmitting the one or more repetitions ofthe PDSCH transmission within a same slot time period, the slot timeperiod occurring within each SPS time period of a set of SPS timeperiods.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the one or morerepetitions of the PDSCH transmission may include operations, features,means, or instructions for transmitting the one or more repetitions ofthe PDSCH transmission within a set of consecutive slot time periodsoccurring within each SPS time period of a set of SPS time periods, eachslot time period of the set of consecutive slot time periods includingtwo repetitions of the PDSCH transmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for configuring a firstaggregation factor as part of the SPS configuration, where a number ofthe set of consecutive slot time periods corresponds to a value of thefirst aggregation factor.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for configuring, based onthe SPS configuration excluding a configuration of a first aggregationfactor, a second aggregation factor as part of a PDSCH configuration,and transmitting the PDSCH configuration to the UE, where a number ofthe set of consecutive slot time periods corresponds to a value of thesecond aggregation factor.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting anindication of the configured repetition scheme as part of the SPSconfiguration.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for transmitting, to theUE, a PDSCH configuration including an indication of the configuredrepetition scheme, where the SPS configuration excludes the indicationof the configured repetition scheme.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a wireless communications system thatsupports techniques for dynamically aggregating a physical downlinkshared channel (PDSCH) for semi-persistent scheduling (SPS) inaccordance with aspects of the present disclosure.

FIG. 2 illustrates an example of a wireless communications system thatsupports techniques for dynamically aggregating a PDSCH for SPS inaccordance with aspects of the present disclosure.

FIGS. 3A, 3B, 3C, and 3D illustrate examples of SPS PDSCH configurationsthat support techniques for dynamically aggregating a PDSCH for SPS inaccordance with aspects of the present disclosure.

FIGS. 4 through 7 illustrate example flow charts that support techniquesfor dynamically aggregating a PDSCH for SPS in accordance with aspectsof the present disclosure.

FIGS. 8 and 9 show block diagrams of devices that support techniques fordynamically aggregating a PDSCH for SPS in accordance with aspects ofthe present disclosure.

FIG. 10 shows a block diagram of a communications manager that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure.

FIG. 11 shows a diagram of a system including a device that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure.

FIGS. 12 and 13 show block diagrams of devices that support techniquesfor dynamically aggregating a PDSCH for SPS in accordance with aspectsof the present disclosure.

FIG. 14 shows a block diagram of a communications manager that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure.

FIG. 15 shows a diagram of a system including a device that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure.

FIGS. 16 through 19 show flowcharts illustrating methods that supporttechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure.

DETAILED DESCRIPTION

In some wireless communications systems, a base station may usesemi-static configurations and dynamic grants to allocate resources to auser equipment (UE) for communications with the base station.Semi-static configurations may be transmitted in radio resource control(RRC) signaling and may in some cases be referred to as configuredgrants (e.g., for uplink transmission) or semi-persistent scheduling(SPS) (e.g., for downlink transmissions). In addition to the semi-staticsignaling that configures such communications, dynamic signaling (e.g.,downlink control information (DCI)) may be used to activate or release aUE's operation using the semi-statically configured communications. Forinstance, once activated (e.g., by DCI having a cyclic redundancy check(CRC) scrambled with a configured scheduling radio network temporaryidentifier (CS-RNTI) and including a new data indicator (NDI) equal tozero), a UE may operate using downlink SPS until the base stationreleases the configuration, at which point the UE may utilize or revertto another communications scheme. In addition, multiple SPSconfigurations may be available to a UE, and the base station maysemi-statically indicate a particular SPS configuration to the UE. Assuch, the downlink SPS transmissions (e.g., on a physical downlinkshared channel (PDSCH)) may be transmitted periodically in accordancewith the indicated SPS configuration.

Retransmission of SPS transmissions (e.g., downlink transmissions thatmay have failed a decoding attempt by the UE and are re-sent by the basestation) may also be scheduled using dynamic signaling from the basestation. For instance, DCI having a CRC scrambled by the CS-RNTI andincluding an NDI equal to one may schedule one or more retransmissionsof an SPS transmission. The UE may accordingly receive a retransmissionof a PDSCH that was previously transmitted as part of the SPSconfiguration based on the received DCI.

Systems may also support various configurations that enable repetitionsof PDSCH (e.g., across consecutive slots). For example, a firstaggregation factor may be generally configured for PDSCH through an RRCconfiguration and a second aggregation factor for PDSCH associated withSPS communications may be configured through another RRC configuration.As multiple different SPS configurations may be possible, the secondaggregation factor may also be specific to a particular SPSconfiguration that is activated via DCI. In addition, the number ofPDSCH repetitions may be dynamically indicated using a time domainresource allocation (TDRA) field within the DCI. In such cases, the TDRAfield within the DCI may indicate a TDRA entry in a table (e.g., a TDRAtable configured via RRC signaling), where some TDRA entries in thetable may indicate a number of repetitions for PDSCH. Thus, while PDSCHrepetitions may be semi-statically configured and indicated (e.g.,through the PDSCH configuration and/or the SPS configuration), the useof the repetitions indicated by the TDRA entries may provide a moredynamic scheme for scheduling repetitions of PDSCH. However, given themultiple configurations for PDSCH repetitions, in addition to multipleSPS configurations, use of TDRA entries that indicate repetitions mayadd complexity in determining how many repetitions of PDSCH will bereceived at a UE.

As described herein, a number of PDSCH repetitions for SPS PDSCH may bedetermined based on the TDRA entries indicated by DCI, the configurationof aggregation factors in one or more RRC configurations, or acombination thereof. For instance, PDSCH repetitions may be determinedbased on a rule that may be based on a priority between a TDRA entryindicated by DCI and repetition factors in an SPS configuration or aPDSCH configuration, or both. Put another way, when a configured TDRAtable includes at least one TDRA entry including a repetition number(e.g., RepNumR16), a UE or base station may determine a number of PDSCHrepetitions (e.g., within each SPS period) based on whether a particularTDRA entry indicated by DCI includes the repetition number.Specifically, in cases where the repetition number is included in theTDRA entry, then a number of PDSCH repetitions may be based on a valueof the repetition number. In other cases, if the TDRA entry indicated inthe DCI does not include the repetition number, one instance of PDSCHmay be received in each SPS period. Additionally or alternatively, ifthe TDRA entry indicated by the DCI (e.g., in the TDRA field) does notinclude the repetition number, then the number of PDSCH repetitions inan SPS period may be based on one or more of a aggregation factor in theSPS configuration (e.g., if configured) or an aggregation factor in thePDSCH configuration (e.g., if configured). As described herein, the useof a rule to determine SPS PDSCH repetitions may utilized for PDSCHtransmissions activated by DCI (e.g., for a particular SPSconfiguration) and for PDSCH retransmissions scheduled by DCI.

In other examples, multiple TCI states may be indicated by a TCI fieldof the DCI that activates an SPS configuration, and a number of SPSPDSCH repetitions may be based on the configuration of a number of TCIindicated by the TCI field and a configured repetition scheme (such as atime division multiplexing (TDM) scheme of a UE). In particular, the TCIfield of the DCI may indicate multiple (e.g., two or more) TCI states,and the UE may be configured with a particular TDM scheme (e.g.,TDMSchemeA). Based on these configurations, the repetitions of the SPSPDSCH may include repetitions of the PDSCH within a same slot, and theSPS PDSCH may be included in one slot per SPS period. An aggregationfactor in the SPS RRC configuration and an aggregation factor in thePDSCH RRC configuration may not be configured for the PDSCH repetitions.For example, the repetitions may only be based on the number of TCIstates and the configured TDM scheme. Additionally or alternatively, theSPS PDSCH repetitions may be repeated within a slot and also repeatedacross multiple consecutive slots (e.g., where each slot includemultiple repetitions of the PDSCH). For instance, the SPS PDSCHrepetitions may include 2N repetitions in N consecutive slots per SPSperiod (e.g., where each slot includes two instances of the PDSCH).Here, N may be based on the aggregation factor in the SPS RRCconfiguration, if configured. If not configured, N may be based on theaggregation factor in the PDSCH RRC configuration. In some examples, theUE may be configured with a TDM scheme that is specific to an SPS RRCconfiguration.

Aspects of the disclosure are initially described in the context ofwireless communications systems. For example, aspects of the disclosureare described in the context of communications between a base stationand a UE. Aspects of the disclosure are further illustrated by anddescribed with reference to apparatus diagrams, SPS PDSCHconfigurations, system diagrams, and decision flowcharts that relate totechniques for dynamically aggregating a physical downlink sharedchannel for SPS.

FIG. 1 illustrates an example of a wireless communications system 100that supports techniques for dynamically aggregating a physical downlinkshared channel for SPS in accordance with aspects of the presentdisclosure. The wireless communications system 100 may include one ormore base stations 105, one or more UEs 115, and a core network 130. Insome examples, the wireless communications system 100 may be a Long TermEvolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pronetwork, or a New Radio (NR) network. In some examples, the wirelesscommunications system 100 may support enhanced broadband communications,ultra-reliable (e.g., mission critical) communications, low latencycommunications, communications with low-cost and low-complexity devices,or any combination thereof.

The base stations 105 may be dispersed throughout a geographic area toform the wireless communications system 100 and may be devices indifferent forms or having different capabilities. The base stations 105and the UEs 115 may wirelessly communicate via one or more communicationlinks 125. Each base station 105 may provide a coverage area 110 overwhich the UEs 115 and the base station 105 may establish one or morecommunication links 125. The coverage area 110 may be an example of ageographic area over which a base station 105 and a UE 115 may supportthe communication of signals according to one or more radio accesstechnologies.

The UEs 115 may be dispersed throughout a coverage area 110 of thewireless communications system 100, and each UE 115 may be stationary,or mobile, or both at different times. The UEs 115 may be devices indifferent forms or having different capabilities. Some example UEs 115are illustrated in FIG. 1 . The UEs 115 described herein may be able tocommunicate with various types of devices, such as other UEs 115, thebase stations 105, or network equipment (e.g., core network nodes, relaydevices, integrated access and backhaul (IAB) nodes, or other networkequipment), as shown in FIG. 1 .

The base stations 105 may communicate with the core network 130, or withone another, or both. For example, the base stations 105 may interfacewith the core network 130 through one or more backhaul links 120 (e.g.,via an S1, N2, N3, or other interface). The base stations 105 maycommunicate with one another over the backhaul links 120 (e.g., via anX2, Xn, or other interface) either directly (e.g., directly between basestations 105), or indirectly (e.g., via core network 130), or both. Insome examples, the backhaul links 120 may be or include one or morewireless links.

One or more of the base stations 105 described herein may include or maybe referred to by a person having ordinary skill in the art as a basetransceiver station, a radio base station, an access point, a radiotransceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or agiga-NodeB (either of which may be referred to as a gNB), a Home NodeB,a Home eNodeB, or other suitable terminology.

A UE 115 may include or may be referred to as a mobile device, awireless device, a remote device, a handheld device, or a subscriberdevice, or some other suitable terminology, where the “device” may alsobe referred to as a unit, a station, a terminal, or a client, amongother examples. A UE 115 may also include or may be referred to as apersonal electronic device such as a cellular phone, a personal digitalassistant (PDA), a tablet computer, a laptop computer, or a personalcomputer. In some examples, a UE 115 may include or be referred to as awireless local loop (WLL) station, an Internet of Things (IoT) device,an Internet of Everything (IoE) device, or a machine type communications(MTC) device, among other examples, which may be implemented in variousobjects such as appliances, or vehicles, meters, among other examples.

The UEs 115 described herein may be able to communicate with varioustypes of devices, such as other UEs 115 that may sometimes act as relaysas well as the base stations 105 and the network equipment includingmacro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations,among other examples, as shown in FIG. 1 .

The UEs 115 and the base stations 105 may wirelessly communicate withone another via one or more communication links 125 over one or morecarriers. The term “carrier” may refer to a set of radio frequencyspectrum resources having a defined physical layer structure forsupporting the communication links 125. For example, a carrier used fora communication link 125 may include a portion of a radio frequencyspectrum band (e.g., a bandwidth part (BWP)) that is operated accordingto one or more physical layer channels for a given radio accesstechnology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layerchannel may carry acquisition signaling (e.g., synchronization signals,system information), control signaling that coordinates operation forthe carrier, user data, or other signaling. The wireless communicationssystem 100 may support communication with a UE 115 using carrieraggregation or multi-carrier operation. A UE 115 may be configured withmultiple downlink component carriers and one or more uplink componentcarriers according to a carrier aggregation configuration. Carrieraggregation may be used with both frequency division duplexing (FDD) andtime division duplexing (TDD) component carriers.

In some examples (e.g., in a carrier aggregation configuration), acarrier may also have acquisition signaling or control signaling thatcoordinates operations for other carriers. A carrier may be associatedwith a frequency channel (e.g., an evolved universal mobiletelecommunication system terrestrial radio access (E-UTRA) absoluteradio frequency channel number (EARFCN)) and may be positioned accordingto a channel raster for discovery by the UEs 115. A carrier may beoperated in a standalone mode where initial acquisition and connectionmay be conducted by the UEs 115 via the carrier, or the carrier may beoperated in a non-standalone mode where a connection is anchored using adifferent carrier (e.g., of the same or a different radio accesstechnology).

The communication links 125 shown in the wireless communications system100 may include uplink transmissions from a UE 115 to a base station105, or downlink transmissions from a base station 105 to a UE 115.Carriers may carry downlink or uplink communications (e.g., in an FDDmode) or may be configured to carry downlink and uplink communications(e.g., in a TDD mode).

A carrier may be associated with a particular bandwidth of the radiofrequency spectrum, and in some examples the carrier bandwidth may bereferred to as a “system bandwidth” of the carrier or the wirelesscommunications system 100. For example, the carrier bandwidth may be oneof a number of determined bandwidths for carriers of a particular radioaccess technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz(MHz)). Devices of the wireless communications system 100 (e.g., thebase stations 105, the UEs 115, or both) may have hardwareconfigurations that support communications over a particular carrierbandwidth or may be configurable to support communications over one of aset of carrier bandwidths. In some examples, the wireless communicationssystem 100 may include base stations 105 or UEs 115 that supportsimultaneous communications via carriers associated with multiplecarrier bandwidths. In some examples, each served UE 115 may beconfigured for operating over portions (e.g., a sub-band, a BWP) or allof a carrier bandwidth.

Signal waveforms transmitted over a carrier may be made up of multiplesubcarriers (e.g., using multi-carrier modulation (MCM) techniques suchas orthogonal frequency division multiplexing (OFDM) or discrete Fouriertransform spread OFDM (DFT-S-OFDM)). In a system employing MCMtechniques, a resource element may include one symbol period (e.g., aduration of one modulation symbol) and one subcarrier, where the symbolperiod and subcarrier spacing are inversely related. The number of bitscarried by each resource element may depend on the modulation scheme(e.g., the order of the modulation scheme, the coding rate of themodulation scheme, or both). Thus, the more resource elements that a UE115 receives and the higher the order of the modulation scheme, thehigher the data rate may be for the UE 115. A wireless communicationsresource may refer to a combination of a radio frequency spectrumresource, a time resource, and a spatial resource (e.g., spatial layersor beams), and the use of multiple spatial layers may further increasethe data rate or data integrity for communications with a UE 115.

One or more numerologies for a carrier may be supported, where anumerology may include a subcarrier spacing (Δf) and a cyclic prefix. Acarrier may be divided into one or more BWPs having the same ordifferent numerologies. In some examples, a UE 115 may be configuredwith multiple BWPs. In some examples, a single BWP for a carrier may beactive at a given time and communications for the UE 115 may berestricted to one or more active BWPs.

The time intervals for the base stations 105 or the UEs 115 may beexpressed in multiples of a basic time unit which may, for example,refer to a sampling period of T_(S)=1/(Δf_(max)·N_(f)) seconds, whereΔf_(max) may represent the maximum supported subcarrier spacing, andN_(f) may represent the maximum supported discrete Fourier transform(DFT) size. Time intervals of a communications resource may be organizedaccording to radio frames each having a specified duration (e.g., 10milliseconds (ms)). Each radio frame may be identified by a system framenumber (SFN) (e.g., ranging from 0 to 1023).

Each frame may include multiple consecutively numbered subframes orslots, and each subframe or slot may have the same duration. In someexamples, a frame may be divided (e.g., in the time domain) intosubframes, and each subframe may be further divided into a number ofslots. Alternatively, each frame may include a variable number of slots,and the number of slots may depend on subcarrier spacing. Each slot mayinclude a number of symbol periods (e.g., depending on the length of thecyclic prefix prepended to each symbol period). In some wirelesscommunications systems 100, a slot may further be divided into multiplemini-slots containing one or more symbols. Excluding the cyclic prefix,each symbol period may contain one or more (e.g., N_(f)) samplingperiods. The duration of a symbol period may depend on the subcarrierspacing or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallestscheduling unit (e.g., in the time domain) of the wirelesscommunications system 100 and may be referred to as a transmission timeinterval (TTI). In some examples, the TTI duration (e.g., the number ofsymbol periods in a TTI) may be variable. Additionally or alternatively,the smallest scheduling unit of the wireless communications system 100may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

Physical channels may be multiplexed on a carrier according to varioustechniques. A physical control channel and a physical data channel maybe multiplexed on a downlink carrier, for example, using one or more oftime division multiplexing (TDM) techniques, frequency divisionmultiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A controlregion (e.g., a control resource set (CORESET)) for a physical controlchannel may be defined by a number of symbol periods and may extendacross the system bandwidth or a subset of the system bandwidth of thecarrier. One or more control regions (e.g., CORESETs) may be configuredfor a set of the UEs 115. For example, one or more of the UEs 115 maymonitor or search control regions for control information according toone or more search space sets, and each search space set may include oneor multiple control channel candidates in one or more aggregation levelsarranged in a cascaded manner. An aggregation level for a controlchannel candidate may refer to a number of control channel resources(e.g., control channel elements (CCEs)) associated with encodedinformation for a control information format having a given payloadsize. Search space sets may include common search space sets configuredfor sending control information to multiple UEs 115 and UE-specificsearch space sets for sending control information to a specific UE 115.

Each base station 105 may provide communication coverage via one or morecells, for example a macro cell, a small cell, a hot spot, or othertypes of cells, or any combination thereof. The term “cell” may refer toa logical communication entity used for communication with a basestation 105 (e.g., over a carrier) and may be associated with anidentifier for distinguishing neighboring cells (e.g., a physical cellidentifier (PCID), a virtual cell identifier (VCID), or others). In someexamples, a cell may also refer to a geographic coverage area 110 or aportion of a geographic coverage area 110 (e.g., a sector) over whichthe logical communication entity operates. Such cells may range fromsmaller areas (e.g., a structure, a subset of structure) to larger areasdepending on various factors such as the capabilities of the basestation 105. For example, a cell may be or include a building, a subsetof a building, or exterior spaces between or overlapping with geographiccoverage areas 110, among other examples.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by theUEs 115 with service subscriptions with the network provider supportingthe macro cell. A small cell may be associated with a lower-powered basestation 105, as compared with a macro cell, and a small cell may operatein the same or different (e.g., licensed, unlicensed) frequency bands asmacro cells. Small cells may provide unrestricted access to the UEs 115with service subscriptions with the network provider or may providerestricted access to the UEs 115 having an association with the smallcell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115associated with users in a home or office). A base station 105 maysupport one or multiple cells and may also support communications overthe one or more cells using one or multiple component carriers.

In some examples, a carrier may support multiple cells, and differentcells may be configured according to different protocol types (e.g.,MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that mayprovide access for different types of devices.

In some examples, a base station 105 may be movable and thereforeprovide communication coverage for a moving geographic coverage area110. In some examples, different geographic coverage areas 110associated with different technologies may overlap, but the differentgeographic coverage areas 110 may be supported by the same base station105. In other examples, the overlapping geographic coverage areas 110associated with different technologies may be supported by differentbase stations 105. The wireless communications system 100 may include,for example, a heterogeneous network in which different types of thebase stations 105 provide coverage for various geographic coverage areas110 using the same or different radio access technologies.

The wireless communications system 100 may support synchronous orasynchronous operation. For synchronous operation, the base stations 105may have similar frame timings, and transmissions from different basestations 105 may be approximately aligned in time. For asynchronousoperation, the base stations 105 may have different frame timings, andtransmissions from different base stations 105 may, in some examples,not be aligned in time. The techniques described herein may be used foreither synchronous or asynchronous operations.

Some UEs 115, such as MTC or IoT devices, may be low cost or lowcomplexity devices and may provide for automated communication betweenmachines (e.g., via Machine-to-Machine (M2M) communication). M2Mcommunication or MTC may refer to data communication technologies thatallow devices to communicate with one another or a base station 105without human intervention. In some examples, M2M communication or MTCmay include communications from devices that integrate sensors or metersto measure or capture information and relay such information to acentral server or application program that makes use of the informationor presents the information to humans interacting with the applicationprogram. Some UEs 115 may be designed to collect information or enableautomated behavior of machines or other devices. Examples ofapplications for MTC devices include smart metering, inventorymonitoring, water level monitoring, equipment monitoring, healthcaremonitoring, wildlife monitoring, weather and geological eventmonitoring, fleet management and tracking, remote security sensing,physical access control, and transaction-based business charging.

Some UEs 115 may be configured to employ operating modes that reducepower consumption, such as half-duplex communications (e.g., a mode thatsupports one-way communication via transmission or reception, but nottransmission and reception simultaneously). In some examples,half-duplex communications may be performed at a reduced peak rate.Other power conservation techniques for the UEs 115 include entering apower saving deep sleep mode when not engaging in active communications,operating over a limited bandwidth (e.g., according to narrowbandcommunications), or a combination of these techniques. For example, someUEs 115 may be configured for operation using a narrowband protocol typethat is associated with a defined portion or range (e.g., set ofsubcarriers or resource blocks (RBs)) within a carrier, within aguard-band of a carrier, or outside of a carrier.

The wireless communications system 100 may be configured to supportultra-reliable communications or low-latency communications, or variouscombinations thereof. For example, the wireless communications system100 may be configured to support ultra-reliable low-latencycommunications (URLLC) or mission critical communications. The UEs 115may be designed to support ultra-reliable, low-latency, or criticalfunctions (e.g., mission critical functions). Ultra-reliablecommunications may include private communication or group communicationand may be supported by one or more mission critical services such asmission critical push-to-talk (MCPTT), mission critical video (MCVideo),or mission critical data (MCData). Support for mission criticalfunctions may include prioritization of services, and mission criticalservices may be used for public safety or general commercialapplications. The terms ultra-reliable, low-latency, mission critical,and ultra-reliable low-latency may be used interchangeably herein.

In some examples, a UE 115 may also be able to communicate directly withother UEs 115 over a device-to-device (D2D) communication link 135(e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115utilizing D2D communications may be within the geographic coverage area110 of a base station 105. Other UEs 115 in such a group may be outsidethe geographic coverage area 110 of a base station 105 or be otherwiseunable to receive transmissions from a base station 105. In someexamples, groups of the UEs 115 communicating via D2D communications mayutilize a one-to-many (1:M) system in which each UE 115 transmits toevery other UE 115 in the group. In some examples, a base station 105facilitates the scheduling of resources for D2D communications. In othercases, D2D communications are carried out between the UEs 115 withoutthe involvement of a base station 105.

In some systems, the D2D communication link 135 may be an example of acommunication channel, such as a sidelink communication channel, betweenvehicles (e.g., UEs 115). In some examples, vehicles may communicateusing vehicle-to-everything (V2X) communications, vehicle-to-vehicle(V2V) communications, or some combination of these. A vehicle may signalinformation related to traffic conditions, signal scheduling, weather,safety, emergencies, or any other information relevant to a V2X system.In some examples, vehicles in a V2X system may communicate with roadsideinfrastructure, such as roadside units, or with the network via one ormore network nodes (e.g., base stations 105) using vehicle-to-network(V2N) communications, or with both.

The core network 130 may provide user authentication, accessauthorization, tracking, Internet Protocol (IP) connectivity, and otheraccess, routing, or mobility functions. The core network 130 may be anevolved packet core (EPC) or 5G core (5GC), which may include at leastone control plane entity that manages access and mobility (e.g., amobility management entity (MME), an access and mobility managementfunction (AMF)) and at least one user plane entity that routes packetsor interconnects to external networks (e.g., a serving gateway (S-GW), aPacket Data Network (PDN) gateway (P-GW), or a user plane function(UPF)). The control plane entity may manage non-access stratum (NAS)functions such as mobility, authentication, and bearer management forthe UEs 115 served by the base stations 105 associated with the corenetwork 130. User IP packets may be transferred through the user planeentity, which may provide IP address allocation as well as otherfunctions. The user plane entity may be connected to the networkoperators IP services 150. The operators IP services 150 may includeaccess to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS),or a Packet-Switched Streaming Service.

Some of the network devices, such as a base station 105, may includesubcomponents such as an access network entity 140, which may be anexample of an access node controller (ANC). Each access network entity140 may communicate with the UEs 115 through one or more other accessnetwork transmission entities 145, which may be referred to as radioheads, smart radio heads, or transmission/reception points (TRPs). Eachaccess network transmission entity 145 may include one or more antennapanels. In some configurations, various functions of each access networkentity 140 or base station 105 may be distributed across various networkdevices (e.g., radio heads and ANCs) or consolidated into a singlenetwork device (e.g., a base station 105).

The wireless communications system 100 may operate using one or morefrequency bands, for example, in the range of 300 megahertz (MHz) to 300gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known asthe ultra-high frequency (UHF) region or decimeter band because thewavelengths range from approximately one decimeter to one meter inlength. The UHF waves may be blocked or redirected by buildings andenvironmental features, but the waves may penetrate structuressufficiently for a macro cell to provide service to the UEs 115 locatedindoors. The transmission of UHF waves may be associated with smallerantennas and shorter ranges (e.g., less than 100 kilometers) compared totransmission using the smaller frequencies and longer waves of the highfrequency (HF) or very high frequency (VHF) portion of the spectrumbelow 300 MHz.

The wireless communications system 100 may also operate in a super highfrequency (SHF) region using frequency bands from 3 GHz to 30 GHz, alsoknown as the centimeter band, or in an extremely high frequency (EHF)region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as themillimeter band. In some examples, the wireless communications system100 may support millimeter wave (mmW) communications between the UEs 115and the base stations 105, and EHF antennas of the respective devicesmay be smaller and more closely spaced than UHF antennas. In someexamples, this may facilitate use of antenna arrays within a device. Thepropagation of EHF transmissions, however, may be subject to evengreater atmospheric attenuation and shorter range than SHF or UHFtransmissions. The techniques disclosed herein may be employed acrosstransmissions that use one or more different frequency regions, anddesignated use of bands across these frequency regions may differ bycountry or regulating body.

The wireless communications system 100 may utilize both licensed andunlicensed radio frequency spectrum bands. For example, the wirelesscommunications system 100 may employ License Assisted Access (LAA),LTE-Unlicensed (LTE-U) radio access technology, or NR technology in anunlicensed band such as the 5 GHz industrial, scientific, and medical(ISM) band. When operating in unlicensed radio frequency spectrum bands,devices such as the base stations 105 and the UEs 115 may employ carriersensing for collision detection and avoidance. In some examples,operations in unlicensed bands may be based on a carrier aggregationconfiguration in conjunction with component carriers operating in alicensed band (e.g., LAA). Operations in unlicensed spectrum may includedownlink transmissions, uplink transmissions, P2P transmissions, or D2Dtransmissions, among other examples.

A base station 105 or a UE 115 may be equipped with multiple antennas,which may be used to employ techniques such as transmit diversity,receive diversity, multiple-input multiple-output (MIMO) communications,or beamforming. The antennas of a base station 105 or a UE 115 may belocated within one or more antenna arrays or antenna panels, which maysupport MIMO operations or transmit or receive beamforming. For example,one or more base station antennas or antenna arrays may be co-located atan antenna assembly, such as an antenna tower. In some examples,antennas or antenna arrays associated with a base station 105 may belocated in diverse geographic locations. A base station 105 may have anantenna array with a number of rows and columns of antenna ports thatthe base station 105 may use to support beamforming of communicationswith a UE 115. Likewise, a UE 115 may have one or more antenna arraysthat may support various MIMO or beamforming operations. Additionally oralternatively, an antenna panel may support radio frequency beamformingfor a signal transmitted via an antenna port.

The base stations 105 or the UEs 115 may use MIMO communications toexploit multipath signal propagation and increase the spectralefficiency by transmitting or receiving multiple signals via differentspatial layers. Such techniques may be referred to as spatialmultiplexing. The multiple signals may, for example, be transmitted bythe transmitting device via different antennas or different combinationsof antennas. Likewise, the multiple signals may be received by thereceiving device via different antennas or different combinations ofantennas. Each of the multiple signals may be referred to as a separatespatial stream and may carry bits associated with the same data stream(e.g., the same codeword) or different data streams (e.g., differentcodewords). Different spatial layers may be associated with differentantenna ports used for channel measurement and reporting. MIMOtechniques include single-user MIMO (SU-MIMO), where multiple spatiallayers are transmitted to the same receiving device, and multiple-userMIMO (MU-MIMO), where multiple spatial layers are transmitted tomultiple devices.

Beamforming, which may also be referred to as spatial filtering,directional transmission, or directional reception, is a signalprocessing technique that may be used at a transmitting device or areceiving device (e.g., a base station 105, a UE 115) to shape or steeran antenna beam (e.g., a transmit beam, a receive beam) along a spatialpath between the transmitting device and the receiving device.Beamforming may be achieved by combining the signals communicated viaantenna elements of an antenna array such that some signals propagatingat particular orientations with respect to an antenna array experienceconstructive interference while others experience destructiveinterference. The adjustment of signals communicated via the antennaelements may include a transmitting device or a receiving deviceapplying amplitude offsets, phase offsets, or both to signals carriedvia the antenna elements associated with the device. The adjustmentsassociated with each of the antenna elements may be defined by abeamforming weight set associated with a particular orientation (e.g.,with respect to the antenna array of the transmitting device orreceiving device, or with respect to some other orientation).

A base station 105 or a UE 115 may use beam sweeping techniques as partof beam forming operations. For example, a base station 105 may usemultiple antennas or antenna arrays (e.g., antenna panels) to conductbeamforming operations for directional communications with a UE 115.Some signals (e.g., synchronization signals, reference signals, beamselection signals, or other control signals) may be transmitted by abase station 105 multiple times in different directions. For example,the base station 105 may transmit a signal according to differentbeamforming weight sets associated with different directions oftransmission. Transmissions in different beam directions may be used toidentify (e.g., by a transmitting device, such as a base station 105, orby a receiving device, such as a UE 115) a beam direction for latertransmission or reception by the base station 105.

Some signals, such as data signals associated with a particularreceiving device, may be transmitted by a base station 105 in a singlebeam direction (e.g., a direction associated with the receiving device,such as a UE 115). In some examples, the beam direction associated withtransmissions along a single beam direction may be determined based on asignal that was transmitted in one or more beam directions. For example,a UE 115 may receive one or more of the signals transmitted by the basestation 105 in different directions and may report to the base station105 an indication of the signal that the UE 115 received with a highestsignal quality or an otherwise acceptable signal quality.

In some examples, transmissions by a device (e.g., by a base station 105or a UE 115) may be performed using multiple beam directions, and thedevice may use a combination of digital precoding or radio frequencybeamforming to generate a combined beam for transmission (e.g., from abase station 105 to a UE 115). The UE 115 may report feedback thatindicates precoding weights for one or more beam directions, and thefeedback may correspond to a configured number of beams across a systembandwidth or one or more sub-bands. The base station 105 may transmit areference signal (e.g., a cell-specific reference signal (CRS), achannel state information reference signal (CSI-RS)), which may beprecoded or unprecoded. The UE 115 may provide feedback for beamselection, which may be a precoding matrix indicator (PMI) orcodebook-based feedback (e.g., a multi-panel type codebook, a linearcombination type codebook, a port selection type codebook). Althoughthese techniques are described with reference to signals transmitted inone or more directions by a base station 105, a UE 115 may employsimilar techniques for transmitting signals multiple times in differentdirections (e.g., for identifying a beam direction for subsequenttransmission or reception by the UE 115) or for transmitting a signal ina single direction (e.g., for transmitting data to a receiving device).

A receiving device (e.g., a UE 115) may try multiple receiveconfigurations (e.g., directional listening) when receiving varioussignals from the base station 105, such as synchronization signals,reference signals, beam selection signals, or other control signals. Forexample, a receiving device may try multiple receive directions byreceiving via different antenna subarrays, by processing receivedsignals according to different antenna subarrays, by receiving accordingto different receive beamforming weight sets (e.g., differentdirectional listening weight sets) applied to signals received atmultiple antenna elements of an antenna array, or by processing receivedsignals according to different receive beamforming weight sets appliedto signals received at multiple antenna elements of an antenna array,any of which may be referred to as “listening” according to differentreceive configurations or receive directions. In some examples, areceiving device may use a single receive configuration to receive alonga single beam direction (e.g., when receiving a data signal). The singlereceive configuration may be aligned in a beam direction determinedbased on listening according to different receive configurationdirections (e.g., a beam direction determined to have a highest signalstrength, highest signal-to-noise ratio (SNR), or otherwise acceptablesignal quality based on listening according to multiple beamdirections).

The wireless communications system 100 may be a packet-based networkthat operates according to a layered protocol stack. In the user plane,communications at the bearer or Packet Data Convergence Protocol (PDCP)layer may be IP-based. A Radio Link Control (RLC) layer may performpacket segmentation and reassembly to communicate over logical channels.A Medium Access Control (MAC) layer may perform priority handling andmultiplexing of logical channels into transport channels. The MAC layermay also use error detection techniques, error correction techniques, orboth to support retransmissions at the MAC layer to improve linkefficiency. In the control plane, the Radio Resource Control (RRC)protocol layer may provide establishment, configuration, and maintenanceof an RRC connection between a UE 115 and a base station 105 or a corenetwork 130 supporting radio bearers for user plane data. At thephysical layer, transport channels may be mapped to physical channels.

The UEs 115 and the base stations 105 may support retransmissions ofdata to increase the likelihood that data is received successfully.Hybrid automatic repeat request (HARQ) feedback is one technique forincreasing the likelihood that data is received correctly over acommunication link 125. A HARQ process may include a combination oferror detection (e.g., using a cyclic redundancy check (CRC)), forwarderror correction (FEC), and retransmission (e.g., automatic repeatrequest (ARQ)). HARQ processes may improve throughput at the MAC layerin poor radio conditions (e.g., low signal-to-noise conditions). In someexamples, a device may support same-slot HARQ feedback, where the devicemay provide HARQ feedback in a specific slot for data received in aprevious symbol in the slot. In other cases, the device may provide HARQfeedback in a subsequent slot, or according to some other time interval.

In wireless communications system 100, a base station 105 may usesemi-static configurations and dynamic grants among other techniques forallocating resources to a UE 115. Semi-static configurations may betransmitted in RRC signaling, which may configure SPS for a UE 115. Inaddition to the semi-static signaling that configures suchcommunications, dynamic signaling (e.g., DCI) may be used to activate orrelease communications. For instance, once activated (e.g., by DCIhaving a CRC scrambled with a CS-RNTI and including an NDI equal tozero), an SPS configuration may be activated for the UE 115. Inaddition, multiple SPS configurations may be available to a UE 115, andthe base station 105 may semi-statically indicate a particular SPSconfiguration to the UE 115. PDSCH transmissions may be transmittedperiodically in accordance with the indicated SPS configuration.Retransmission of SPS transmissions may also be scheduled using dynamicsignaling from the base station 105. For instance, using DCI having aCRC scrambled by the CS-RNTI and including an NDI equal to one, aretransmission of an SPS PDSCH may be scheduled.

Wireless communications system 100 may also support variousconfigurations that enable repetitions of PDSCH (e.g., acrossconsecutive slots). For example, a first aggregation factor may beconfigured for PDSCH through an RRC configuration and a secondaggregation factor for PDSCH associated with SPS communications may beconfigured through another RRC configuration. In addition, the number ofPDSCH repetitions may be dynamically indicated to a UE 115 using a TDRAfield within DCI and the use of the repetitions indicated by the TDRAentries (e.g., where a configured TDRA table may include at least oneTDRA entry that includes a repetition number) may provide a more dynamicscheme for repetitions of PDSCH.

In some examples, a number of PDSCH repetitions for SPS PDSCH may bedetermined based on the TDRA entries indicated by DCI, the configurationof aggregation factors in one or more RRC configurations, or acombination thereof. For instance, PDSCH repetitions may be determinedbased on a rule that may be based on a priority between a TDRA entry andconfigured repetition factors in an SPS configuration or a PDSCHconfiguration, or both. For example, in cases where the repetitionnumber is included in the TDRA entry, then a number of PDSCH repetitionsmay be based on a value of the repetition number. In other cases, if theTDRA entry indicated in the DCI does not include the repetition number,one instance of PDSCH may be received in each SPS period. Additionallyor alternatively, if the TDRA entry indicated by the DCI (e.g., in theTDRA field) does not include the repetition number, then the number ofPDSCH repetitions in an SPS period may be based on an aggregation factorin the SPS configuration (e.g., if configured), an aggregation factor inthe PDSCH configuration, or both.

FIG. 2 illustrates an example of a wireless communications system 200that supports techniques for dynamically aggregating a physical downlinkshared channel for SPS in accordance with aspects of the presentdisclosure. In some examples, wireless communications system 200 mayimplement aspects of wireless communications system 100. For example,wireless communications system 200 may include communications between aUE 115-a and a base station 105-a, which may be examples of a UE 115 anda base station 105 described with reference to FIG. 1 .

Wireless communications system 200 may support multiple SPSconfigurations to increase system capacity and reduce control signalingoverhead. The base station 105-a may transmit, to the UE 115-a, aphysical downlink control channel transmission 205 containing DCI (e.g.,scheduling DCI 210). The base station 105-a may also transmit othercontrol signaling such as RRC signaling. The control channeltransmission, for example, an RRC message, may include various RRCconfigured parameters such as sps-ConfigIndex, periodicity, etc. Inaddition, an SPS configuration may be activated by the controlinformation, such as by DCI 210, and the DCI 210 may include a number ofCRC bits scrambled with a CS-RNTI, and a NDI of the DCI 210 may be equalto zero or one (e.g., NDI=0 may be indicated for activating an SPSconfiguration, whereas NDI=1 may be used for scheduling SPSretransmissions).

Because wireless communications system 200 may use a number of differentSPS configurations, the base station 105-a may repurpose a HARQ processnumber field in the DCI 210 for indicating an activated SPSconfiguration (e.g., sps-ConfigIndex). The SPS configuration may includea number of transmission locations for SPS PDSCH 215 that may beconfigured according to the periodicity 220. The base station 105-a mayalso use the HARQ process number field to indicate a HARQ process ID forretransmitting data. However, in cases where SPS is activated, the HARQprocess ID or HARQ process number may be a function of the time domainsuch that HARQ process IDs may be incremented based on the periodicity220 of the SPS. Each SPS PDSCH 215 may be associated with a differentHARQ process ID, for example, SPS PDSCH 215-a may be associated with aHARQ process ID of 0, SPS PDSCH 215-b may be associated with a HARQprocess ID of 1, SPS PDSCH 215-c may be associated with a HARQ processID of 2, and SPS PDSCH 215-d may be associated with a HARQ process ID of3.

For a retransmission associated with an SPS PDSCH 215, an initialtransmission may be an SPS PDSCH, but if the SPS PDSCH is notsuccessfully decoded, the base station may not be able to send anactivating DCI 210 for a retransmission (e.g., the base station may notsend a DCI with NDI=0 that activates SPS). Instead, the base station105-a may send a scheduling DCI 225 that may schedule retransmission 230with CRC scrambled with CS-RNTI and NDI=1.

Wireless communications system 200 may support data transmissions thatspan multiple slots using an SPS configuration that includes slotaggregation. In some implementations, the UE 115-a may receive anaggregation factor as part of a PDSCH configuration (e.g.,pdsch-AggregationFactor in pdsch-config) in consecutive slots in caseswhere the UE 115-a receives DCI that schedules transmissions orretransmissions of PDSCH 215, or in cases where the UE 115-a receivesDCI that activates SPS. In each of the consecutive slots, a UE 115-a mayreceive a PDSCH transmission occasion (e.g., a repetition of the sametransport block). In some cases, the same symbol allocation (asindicated in the TDRA field of the DCI) may be applied across thepdsch-AggregationFactor in consecutive slots. In such cases, thepdsch-AggregationFactor may have values of 2, 4, 8, etc. In some cases,the UE 115-a may receive a dynamic grant that may schedule a non-SPSPDSCH transmission, activate SPS, or schedule a retransmission of an SPSPDSCH.

In some other implementations, each SPS configuration may be separatelyconfigured with an SPS configuration that includes slot aggregation(e.g., separately configured with pdsch-AggregationFactor insps-config). For example, the pdsch-AggretationFactor may be specific toa given SPS configuration of the multiple SPS configurations that may beconfigured. In cases where a given SPS configuration is activated (e.g.,activated using a DCI with CRC scrambled by CS-RNTI and NDI=0), thevalue for pdsch-AggregationFactor in sps-config for the activated SPSconfiguration may be used for the number of slots used for repetitions.In some other cases where a given SPS configuration is activated (e.g.,activated using a DCI with CRC scrambled by CS-RNTI and NDI=0), thevalue for the pdsch-AggregationFactor in pdsch-config may be used, andis common to all SPS configurations and non-SPS PDSCH transmissions. Forretransmissions of SPS PDSCH (e.g., activated using a DCI with CRCscrambled by CS-RNTI and NDI=1), the pdsch-AggregationFactor inpdsch-config may be used.

In some examples, the number of repetitions of PDSCH 215 (e.g., PDSCHrepetitions) may be indicated dynamically using a TDRA field within DCI,such as scheduling DCI 210. In such cases, the TDRA may indicate a TDRAentry in a table (e.g., pdsch-TimeDomainAllocationList), where some TDRAentries in the table may indicate a number of repetitions for PDSCHtransmissions (e.g., in a column ofpdsch-TimeDomainAllocationList).However, given the multiple configurations for PDSCH repetitions, inaddition to multiple SPS configurations (which may be configuredaccording to a different number of PDSCH repetitions), the repeated TDRAentries may add complexity in determining how many repetitions of PDSCHwill be received at the UE 115-a.

To improve scheduling and overall communications efficiency between thebase station 105-a and the UE 115-a, the number of PDSCH repetitions forSPS PDSCH may be determined based on the configuration of the TDRAentries in DCI 210, the configuration of aggregation factors in one ormore RRC configurations (e.g., sps-config or pdsch-config), or acombination thereof. For instance, as described herein, the number ofrepetitions of PDSCH 215 may be based on a repetition number indicatedby DCI or based on one or more semi-static configurations. As anexample, the UE 115-a may receive, via RRC signaling, an indication ofan SPS configuration (e.g., from a set of SPS configurations) and aPDSCH configuration. The UE 115-a may receive DCI associated with theSPS configuration (e.g., DCI that activates PDSCH transmissions for theSPS configuration or DCI that schedules one or more retransmissions ofan SPS PDSCH 215). An expected number of instances (e.g., repetitions)of an SPS PDSCH 215 (e.g., within a periodicity 220 (an SPSperiodicity)) may be determined using a rule that is based on a prioritybetween various configurations. In some examples, the rule may be usedto identify which configuration may be used to identify the number ofPDSCH repetitions. For example, the number of PDSCH repetitions may beindicated dynamically using a TDRA field within DCI, and a TDRA entry inthe TDRA field may include a repetition number that is used for thenumber of PDSCH repetitions. For example, a number of repetitions inTDRA field may provide or otherwise indicate the number of PDSCHrepetitions. In some examples, the TDRA entry may be from a TDRA tableincluding at least one TDRA entry that includes the repetition number.In some examples, different TDRA entries may include differentrepetition numbers. For example, a first entry in a TDRA table mayindicate a first number of repetitions (e.g., four repetitions), asecond entry may indicate a second number of repetitions (e.g., threerepetitions), and a third entry may not indicate a number of repetitions(e.g., the third entry may not include a repetition number).

In some examples, a first aggregation factor may be configured throughthe PDSCH configuration and/or a second aggregation factor may beconfigured through the SPS configuration. In some cases (such as whenthe TDRA entry does not include the repetition number), one or both ofthe first aggregation factor or the second aggregation factor (e.g., ifconfigured) may be used for determining repetitions of the SPS PDSCH215. In other cases, a single instance of PDSCH 215 may be transmittedbased on the various configurations, for example, as determined by therule.

In some examples, a number of PDSCH repetitions for SPS PDSCH 215 may bedetermined based on a configured repetition scheme for PDSCH and anumber of indicated TCI states in the DCI. In examples in which multipleTCI states are indicated (e.g., by DCI), then multiple (e.g., two)repetitions of the PDSCH 215 may be included in a same slot (e.g., inrespective SPS periods). In other cases, each SPS PDSCH 215 may berepeated multiple (e.g., two) times per slot across a number ofconsecutive slots. Additionally or alternatively, the repetition schememay be configured for a particular SPS configuration, and therepetitions of the PDSCH 215 for SPS (e.g., when activated) may be basedon the configuration-specific repetitions scheme (e.g., as indicated byone or both of the SPS configuration or the PDSCH configuration).

FIGS. 3A, 3B, 3C, and 3D illustrate examples of SPS PDSCH configurations300-a, 300-b, 300-c, and 300-d that support techniques for dynamicallyaggregating a PDSCH for SPS in accordance with aspects of the presentdisclosure. In some examples, SPS PDSCH configurations 300-a through300-d may implement aspects of wireless communications systems 100 and200. For example, the SPS PDSCH configurations 300-a through 300-d maybe configured by a base station 105 and may be implemented by a UE 115described with reference to FIGS. 1 and 2 .

In some cases, such as in the example of SPS PDSCH configuration 300-aillustrated by FIG. 3A, a wireless communications system may supportslot aggregation for SPS transmissions. The slot aggregation may beassociated with a given slot aggregation factor as part of a PDSCHconfiguration (e.g., pdsch-AggregationFactor in pdsch-config). A UE mayreceive transmissions over a PDSCH scheduled by DCI format 1_1, 1_2,etc. In some cases, the UE may receive the DCI in a physical downlinkcontrol channel (PDCCH) with a number of CRC bits scrambled by C-RNTI,MCS-C-RNTI, or CS-RNTI with NDI=1. In such cases, the same symbolallocation may be applied across consecutive slots associated with thepdsch-AggregationFactor. In some other cases, the UE may receive PDSCHscheduled by DCI format 1_1 or 1_2 in a PDCCH with CRC scrambled byCS-RNTI with NDI=0, or in a PDSCH scheduled without corresponding PDCCHtransmission using an SPS configuration activated by DCI format 1_1 or1_2. In such cases, the same symbol allocation may be applied across thepdsch-AggregationFactor in sps-config (if pdsch-AggregationFactor isconfigured for the activated sps-config) or in pdsch-config (ifpdsch-AggregationFactor is not configured for the activated sps-config).In some other cases, the symbol allocation may be indicated by the DCIfor consecutive slots.

The activating DCI 305 may activate the SPS configuration, and mayindicate sps-ConfigIndex=0 using a repurposed HARQ process field in theDCI 305. In addition, the pdsch-AggregationFactor in sps-config (e.g.,for sps-ConfigIndex=0) is 4 repetitions (e.g., 4 SPS PDSCH repetitions310-a. 310-b, 310-c, and 310-d). Further, the pdsch-AggregationFactor inpdsch-config is 2 and may be RRC configured (e.g., 2 slots 325configured for PDSCH transmission, which may be used for aretransmission of the SPS PDSCH).

In some examples, SPS PDSCH configuration 300-b described in FIG. 3B mayimplement dynamic PDSCH (e.g., non-SPS PDSCH) that may include a dynamicindication in DCI 305 that indicates of the number of repetitions forthe PDSCH in consecutive slots. In some examples, the number of PDSCHrepetitions may be indicated dynamically using a time domain resourceallocation (TDRA) field within the DCI 305. In such cases, the TDRAfield indicates a TDRA entry from a table (e.g.,pdsch-TimeDomainAllocationList), where some TDRA entries in the tablemay indicate a number of repetitions for PDSCH (e.g., in a columnofpdsch-TimeDomainAllocationList). In such examples, each TDRA entry mayinclude a number of repetitions (e.g., RepNumR16) in addition to otherparameters such as K0, SLIV, mapping type, etc. In cases where an entryis not configured to include a number of repetitions, a singlerepetition may be assumed. In some examples, the TDRA field in the DCI305 indicates one TDRA entry, and the number of repetitions may beindicated by the DCI 305 through TDRA field. The TDRA table may be usedfor a number of DCI formats, including DCI formats 1_1, 1_2, etc. Incases where the TDRA entry (e.g., an entry in the TDRA table) isconfigured with a number of repetitions (e.g., RepNumR16), the SPS PDSCHmay be transmitted or received based on the configured number ofrepetitions.

As described herein, at least one TDRA table entry is configured with anumber of repetitions (e.g., a repetition number, RepNumR16). That is,the TDRA table includes a plurality of TDRA entries, and at least oneTDRA entry may include the repetition number. If DCI indicates a TDRAentry that includes a number of repetitions, that number of repetitionsmay be used for the number of PDSCH repetitions. In other cases, the DCImay indicate that a TDRA entry that does not contain a number ofrepetitions, and the UE may assume a single repetition. In some othercases, for example, when multiple SPS configurations and RRC parameters(e.g., pdsch-AggregationFactor) are configured per each sps-config, thenetwork may use a different TDRA table than that used for non-SPS PDSCHapplications.

In some examples, the UE may derive a time duration from a periodicitycorresponding to the sps-config, and the UE may use the periodicity toderive a number of repetitions. In such examples, the UE may not beexpected to be indicated by a TDRA entry with RepNumR16 repetitionslarger than a time duration derived by a periodicity P obtained from thecorresponding sps-config.

In some examples, one or more TDRA entry may include a value indicatingnumber of repetitions (e.g., RepNumR16 or another repetition number),and SPS PDSCH may be activated by information in DCI (e.g., DCI that hasCRC scrambled with CS-RNTI with NDI=0). A TDRA field included in the DCImay activate the SPS configuration, and may indicate an entry inpdsch-TimeDomainAllocationList containing a number of repetitions forthe PDSCH. In such cases, the number of repetitions may be indicated byRepNumR16 or another number of repetitions. In other cases, the UE mayassume a single repetition, such as when the TDRA entry does not includeRepNumR16. In some cases, the aggregation factor pdsch-AggregationFactormay be RRC configured per SPS occasion of the multiple SPS occasions. Insome other cases, for example, in cases where an entry contains aconfigured number of repetitions, neither the aggregation factorconfigured in sps-config nor in the pdsch-config may be used,irrespective of the TDRA entry.

In another example, the number of repetitions may be indicated by avalue of the aggregation factor (e.g., pdsch-AggregationFactor) in theactivated SPS configuration. In such examples, the TDRA field in the DCIthat activates the SPS configuration may not indicate the configurednumber of repetitions as an entry in pdsch-TimeDomainAllocationList. Forexample, the aggregation factor (e.g., pdsch-AggregationFactor indicatedin sps-config and in pdsch-config) may not be used in cases where theindicated TDRA entry includes the configured number of repetitions. Inother examples, the pdsch-AggregationFactor in sps-config may be used.In some other examples the pdsch-AggregationFactor may not be insps-config that is used, and the pdsch-AggregationFactor in pdsch-configmay instead be used. In yet other cases, the number of repetitions maybe 1 (e.g., in cases where the RRC parameter pdsch-AggregationFactor isnot configured in the activated sps-config or pdsch-config).

In some aspects, the number of repetitions may be indicated by theaggregation factor in the SPS configuration. If pdsch-AggregationFactoris not configured in sps-config, the number of repetitions may beindicated by pdsch-AggregationFactor in pdsch-config. In yet othercases, the number of repetitions may be assumed to be one wherepdsch-AggregationFactor is not configured in sps-config or pdsch-configthat are activated. In such cases, the determination of the number ofrepetitions may not be based on the TDRA table or a TDRA entrycontaining a configured number of repetitions.

In some examples, a wireless communications system may scheduleretransmissions associated with an initial SPS PDSCH transmission. Forretransmission of an SPS PDSCH (e.g., that is scheduled by DCI with CRCscrambled with CS-RNTI with NDI=1). In some cases, a TDRA field includedin the DCI that schedules the retransmission, and indicates an entry inpdsch-TimeDomainAllocationList containing a number of repetitions (e.g.,RepNumR16). In other cases (e.g., in cases where an entry does notinclude the configured number of repetitions), the UE may assume asingle repetition for the retransmission. The aggregation factor in someexamples may be RRC configured per SPS occasion (e.g., individually foreach SPS occasion) of the multiple SPS occasions. In some other cases,for example, where an entry contains the configured number ofrepetitions, the pdsch-AggregationFactor included in sps-config and inpdsch-config may not be used (e.g., irrespective of the indicated TDRAentry).

In some examples, an aggregation factor for the PDSCH (e.g.,pdsch-AggregationFactor) may be configured as part of a PDSCconfiguration of an SPS configuration (e.g., per SPS-Config). In somecases, if a UE is configured with a higher layer parameter associatedwith the number of repetitions of the PDSCH (e.g., repetitionNumber) orif the UE is configured by another higher layer parameter (e.g.,repetitionScheme) associated with one or more multiplexing schemes(e.g., ‘fdmSchemeA’, ‘fdmSchemeB,’ ‘tdmSchemeA’), the UE may not expectto be configured with the aggregation factor (e.g.,pdsch-AggregationFactor). In such cases, the aggregation factor (e.g.,pdsch-AggregationFactor) may not be configured as part of a PDSCHconfiguration or as part of an SPS configuration.

In some other cases, the number of repetitions for a retransmission maybe determined by an aggregation factor in a PDSCH configuration (e.g.,if pdsch-config is configured). For example, if thepdsch-AggregationFactor is not configured in the sps-config and is alsonot configured in pdsch-config, the number of repetitions for theretransmission may be assumed to be 1. In this case, the determinationof the number of repetitions may not be based on the TDRA table or aTDRA entry containing the number of repetitions.

In the example of FIG. 3B, an activating DCI 330 may indicate a TDRAentry with a number of repetitions (e.g., RepNumR16=3, such that eachSPS PDSCH location 340 has 3 repetitions). The activating DCI 330 may insome cases repurpose a HARQ process field to indicate a value forsps-ConfigIndex, for example, where sps-ConfigIndex=0. In examples wheresps-ConfigIndex=0, the pdsch-AggregationFactor in the SPS configurationmay be equal to 4 (e.g., 4 SPS PDSCH locations 340-a. 340-b, 340-c,330-d). In the example of FIG. 3B, each SPS PDSCH location may beassociated with a different HARQ process ID. For example, PDSCH location340-a may be associated with HARQ process ID 0, PDSCH location 340-b maybe associated with HARQ process ID 1, PDSCH location 340-c may beassociated with HARQ process ID 2, and PDSCH location 340-d may beassociated with HARQ process ID 3.

A DCI 345 may schedule a retransmission associated with the datatransmitted in PDSCH location 340-b (e.g., HARQ process ID=1). In suchcases, the indicated TDRA entry may not include a number of repetitions(e.g., TDRA entry may not have RepNumR16) and the DCI 345 may scheduleone repetition for the retransmission.

In some cases, a PDSCH may be scheduled by a given DCI format (e.g., DCIformat 1_1 or 1_2) in a PDCCH (e.g., a PDCCH with CRC scrambled byCS-RNTI with NDI=0), and in some other cases a PDSCH may be scheduledwithout a corresponding PDCCH transmission using an SPS configurationand activated by DCI. In some examples, the UE may not be configuredwith the time duration for the reception of repetitions (e.g., a numberof repetitions given by pdsch-AggregationFactor), in an SPS or PDSCHconfiguration. In some examples, the number of repetitions may not belarger than the time duration derived by the periodicity P obtained fromthe corresponding SPS configuration. For example, the number ofrepetitions may not be larger than the periodicity 335. Accordingly, thenumber of repetitions in a first period of the periodicity 335 may notoverlap with a number of repetitions in a second period of theperiodicity. In cases where the number of repetitions exceeds the timeduration of the periodicity, the UE may not receive the PDSCH, or mayotherwise determine an error.

In FIG. 3C, a wireless communications network may support intra-slotrepetition, where more than one repetition may occur within a slot(e.g., TDMSchemeA or mini-slot based repetition).

In some examples, a UE may be configured by the higher layer parameterRepSchemeEnabler set to one of a number of multi-TRP schemes. The UE maybe indicated with two TCI states in a codepoint of the DCI field andDM-RS port(s) within one code division multiplexing (CDM) group in theDCI field. In some cases, two TCI states may be indicated in a DCI andthe UE may be set to a first multi-TRP scheme. The number of TCI statesmay in some examples correspond to a number of repetitions (e.g., afirst repetition corresponding to a first TCI state and a secondrepetition corresponding to a second TCI state). The UE may receive twoPDSCH transmission occasions of the same TB, with each TCI stateassociated with a PDSCH transmission occasion which has non-overlappingtime domain resource allocation with respect to the other PDSCHtransmission occasion. In some examples, both PDSCH transmissionoccasions may be received within a single slot.

In cases where two TCI states are indicated in a codepoint of the TCIfield of the DCI 355, a UE may transmit two repetitions within a singleslot. In such cases, the UE may apply the first TCI state to the firstrepetition, and may apply the second TCI state to the second repetition.In some cases, the two repetitions may have the same length as indicatedby the TDRA field of the DCI.

As illustrated by FIG. 3C, SPS PDSCH may be activated by a DCI 355(where DCI 355 has a number of CRC bits scrambled with CS-RNTI, andNDI=0). In addition, two TCI states may be indicated by the TCI field ofthe DCI 355, and the UE is configured with a first multi-TRP scheme(e.g., TDMSchemeA). In some cases, each SPS PDSCH may include tworepetitions within the same slot 360, and the SPS PDSCH is configured inone slot per SPS period 370. In such examples, the UE may not use theaggregation factor in in the SPS or PDSCH configurations.

In another example, each SPS PDSCH may include 2*N repetitions in Nconsecutive slots, each slot containing 2 repetitions (e.g., inter-slotand intra-slot repetition), within an SPS periodicity 390. N may be avalue of the aggregation factor configured for the sps-config, or insome other cases N may be the value of the aggregation factor configuredfor the pdsch-config.

For example, as illustrated in FIG. 3D, the DCI 375 may indicate two TCIstates with sps-ConfigIndex=0, which may be indicated in a HARQ processfield that is repurposed in the DCI 375. Each SPS PDSCH 380 may havefour repetitions: two repetitions in the first slot 385, and tworepetitions in the second slot 395 (e.g., because thepdsch-AggregationFactor=2). In some examples, the first slot 385 and thesecond slot 395 may be consecutive slots. In addition, each SPS PDSCH380 may be associated with a different HARQ process ID (e.g., PDSCH380-a may be associated with a HARQ process ID=0, and PDSCH 380-b may beassociated with HARQ process ID=1). Within each slot, the first tworepetitions (e.g., in slot 360) may be associated with the first TCIstate and the second two repetitions (e.g., in slot 365) may beassociated with the second TCI state. In another example, the firstrepetition and the third repetition (e.g., first repetition in each slotof the multiple slots) may be associated with the first TCI state, andthe second repetition and the fourth repetition (second repetition ineach slot of the multiple slots) may be associated with the second TCIstate.

In some other examples, an RRC parameter (e.g., RepSchemeEnabler orrepetitionScheme (which may be set to a configuration such as one ofFDMSchemeA, FDMSchemeB, TDMSchemeA)) may be separately configured perSPS configuration. When an SPS configuration is activated, the PDSCHscheme that is implemented may be determined based on the RRC parameterin an SPS configuration (e.g., sps-config), or in a PDSCH configuration(e.g., if sps-config is not configured). In such cases, the UE may notexpect to be configured with an aggregation factor (e.g.,pdsch-AggregationFactor) for PDSCH.

FIG. 4 illustrates an example of a flow chart 400 that supportstechniques for dynamically aggregating a physical downlink sharedchannel for SPS in accordance with aspects of the present disclosure. Insome examples, flow chart 400 may implement aspects of wirelesscommunications system 100. In some examples, flow chart 400 may beimplemented by a UE, such as a UE described with reference to FIGS. 1and 2 . However, it is also noted that aspects of the flow chart 400 maybe used by a base station, such as a base station 105 described withreference to FIGS. 1 and 2 , when determining a number of repetitionsfor transmitting PDSCH.

At 405, the UE may receive a PDSCH configuration from a base station. Inaddition, at 410 the UE may receive an SPS configuration from a set ofone or more SPS configurations. In some examples, the PDSCHconfiguration and the SPS configuration are received via RRC signaling.

At 415, the UE may receive DCI associated with a PDSCH transmission forthe SPS configuration. In some cases, the DCI may have a CRC that isscrambled by a CS-RNTI, and may have an NDI equal to zero. In someexamples, the DCI may activate the SPS configuration. In some otherexamples the DCI has a CRC that is scrambled by a CS-RNTI with an NDIequal to one, and DCI may schedule a PDSCH transmission that includes aretransmission of the SPS PDSCH. The DCI may have a number of differentformats (e.g., DCI format 1_1, DCI format 1_2, etc.).

At 420, the UE may determine, based on a rule, a repetition number for anumber of expected instances of the PDSCH transmission, wherein the ruleis based on a priority between a TDRA entry indicated by the DCI and atleast one of the PDSCH configuration or the SPS configuration. In somecases, UE may receive a TDRA table including the TDRA entry via RRCsignaling. The TDRA entry may in some examples be from a TDRA table thatcomprises a number of TDRA entries, and where at least one TDRA entry ofthe number of TDRA entries includes the repetition number. In someexamples, the UE may determine whether the TDRA entry includes therepetition number, and the repetition number is indicated by the entryof the TDRA table.

At 430 the UE may determine that the TDRA entry indicated by the DCIincludes the repetition number. In addition, the UE may identify anumber of repetitions of the PDSCH transmission based on a value of therepetition number, where two or more instances of the PDSCH transmissionare received based on the identified number of repetitions. In someexamples, the number of repetitions of the PDSCH transmission may occurwithin a time period that is less than or equal to the SPS time period.

At 425 the UE may determine that the TDRA entry indicated by the DCIexcludes the repetition number. The UE may determine that the number ofexpected instances (e.g., repetitions) of the PDSCH transmission isequal to one based on the TDRA entry excluding the repetition number,where a single instance of the PDSCH transmission is received based onthe number of expected instances.

Based on determining whether the TDRA entry includes the repetitionnumber at 420, the UE may determine that the number of repetitions isequal to 1 (e.g., at 425), or the UE may us the value of the repetitionnumber for a number of repetitions of the PDSCH (e.g., at 430). At 435,the UE may receive, within each SPS time period of a number of SPS timeperiods, one or more instances of the PDSCH transmission in accordancewith the determined repetition number. In some examples, the one or moreinstances of the PDSCH transmission are received in a different slottime period of a plurality of consecutive slot time periods.

FIG. 5 illustrates an example of a flow chart 500 that supportstechniques for dynamically aggregating a physical downlink sharedchannel for SPS in accordance with aspects of the present disclosure. Insome examples, flow chart 500 may implement aspects of wirelesscommunications system 100. In some examples, flow chart 500 may beimplemented by a UE, such as a UE described with reference to FIGS. 1and 2 . However, it is also noted that aspects of the flow chart 500 maybe used by a base station, such as a base station 105 described withreference to FIGS. 1 and 2 , when determining a number of repetitionsfor transmitting PDSCH.

At 505, the UE may receive a PDSCH configuration from a base station. Inaddition, at 510, the UE may receive an SPS configuration from a set ofone or more SPS configurations. In some examples, the PDSCHconfiguration and the SPS configuration may be received via RRCsignaling. In some examples, the SPS configuration may include a firstaggregation factor, and the UE may identify a number of repetitions of aPDSCH transmission corresponding to a value of the first aggregationfactor, wherein two or more instances of the PDSCH transmission arereceived based on the identified number of repetitions.

At 515, the UE may receive DCI associated with a PDSCH transmission forthe SPS configuration. In some cases, the DCI may have a CRC that isscrambled by a CS-RNTI, and may have an NDI equal to zero. In someexamples, the DCI may activate the SPS configuration. In some otherexamples the DCI has a CRC that is scrambled by a CS-RNTI with an NDIequal to one, and DCI may schedule a PDSCH transmission that includes aretransmission of the SPS PDSCH. The DCI may have a number of differentformats (e.g., DCI format 1_1, DCI format 1_2, etc.).

At 520, the UE may determine, based on a rule, a repetition number for anumber of expected instances of the PDSCH transmission, where the rulemay be based on a priority between a TDRA entry indicated by the DCI andat least one of the PDSCH configuration or the SPS configuration. Insome cases, UE may receive a TDRA table including the TDRA entry via RRCsignaling. The TDRA entry may in some examples be from a TDRA table thatcomprises a number of TDRA entries, and where at least one TDRA entry ofthe number of TDRA entries includes the repetition number. In someexamples, the UE may determine whether the TDRA entry includes therepetition number, and the repetition number may be indicated by theentry of the TDRA table.

At 525 the UE may determine that the TDRA entry indicated by the DCIincludes the repetition number. In addition, the UE may identify anumber of repetitions of the PDSCH transmission based on a value of therepetition number, and the UE may receive the SPS PDSCH according to thenumber of repetitions included in the DCI at 560.

At 530, the UE may determine that the TDRA entry does not include therepetition number. The UE may identify a configuration of the firstaggregation factor from the SPS configuration and may identify a numberof repetitions of the PDSCH transmission at 535 corresponding to a valueof the first aggregation factor. In some examples, two or more instances(e.g., repetitions) of the PDSCH transmission are received based on theidentified number of repetitions at 560. In some cases, the UE mayidentify the number of repetitions of the PDSCH transmissioncorresponding to the first aggregation factor, where two or moreinstances of the PDSCH transmission are received based on the identifiednumber of repetitions.

At 540, the UE may determine that a TDRA entry excludes the repetitionnumber and that the SPS configuration excludes the configuration of thefirst aggregation factor. The UE may identify a configuration of asecond aggregation factor from the PDSCH configuration based on theexclusion of the first aggregation factor. The UE may identify a numberof repetitions of the PDSCH transmission corresponding to a value of thesecond aggregation factor at 545, where two or more instances (e.g.,repetitions) of the PDSCH transmission are received based on theidentified number of repetitions at 560.

At 550, the UE may determine, based on the TDRA entry excluding therepetition number, that the SPS configuration excludes a configurationof a first aggregation factor. The UE may determine, based on the SPSconfiguration excluding the configuration of the first aggregationfactor, that the PDSCH configuration also excludes a configuration of asecond aggregation factor. The UE may further determine that the numberof expected instances of the PDSCH transmission is equal to one based onthe TDRA entry excluding the repetition number, the SPS configurationexcluding the configuration of the first aggregation factor, and thePDSCH configuration excluding the configuration of the secondaggregation factor.

The UE may determine that a single instance of the PDSCH transmission isreceived based on the number of expected instances at 560. For example,the UE may determine that the number of expected instances of the PDSCHtransmission is equal to one based on the SPS configuration excludingthe configuration of the first aggregation factor and the PDSCHconfiguration excluding the configuration of the second aggregationfactor, wherein a single instance of the PDSCH transmission is receivedbased on the number of expected instances.

FIG. 6 illustrates an example of a flow chart 600 that supportstechniques for dynamically aggregating a physical downlink sharedchannel for SPS in accordance with aspects of the present disclosure. Insome examples, flow chart 600 may implement aspects of wirelesscommunications system 100. In some examples, flow chart 600 may beimplemented by a UE, such as a UE described with reference to FIGS. 1and 2 . However, it is also noted that aspects of the flow chart 600 maybe used by a base station, such as a base station 105 described withreference to FIGS. 1 and 2 , when determining a number of repetitionsfor transmitting PDSCH.

At 605, the UE may receive a PDSCH configuration from a base station. Inaddition, at 610, the UE may receive an SPS configuration from a set ofone or more SPS configurations. In some examples, the PDSCHconfiguration and the SPS configuration are received via RRC signaling.In some examples, the SPS configuration may include a first aggregationfactor, and the UE may identify a number of repetitions of a PDSCHtransmission corresponding to a value of the first aggregation factor,wherein two or more instances of the PDSCH transmission are receivedbased on the identified number of repetitions.

At 615, the UE may receive DCI associated with a PDSCH transmission forthe SPS configuration. In some cases, the DCI may have a CRC that isscrambled by a CS-RNTI, and may have an NDI equal to zero. In someexamples, the DCI may activate the SPS configuration. In some otherexamples the DCI has a CRC that is scrambled by a CS-RNTI with an NDIequal to one, and DCI may schedule a PDSCH transmission that includes aretransmission of the SPS PDSCH. The DCI may have a number of differentformats (e.g., DCI format 1_1, DCI format 1_2, etc.).

At 620, the UE may determine, based on a rule, a repetition number for anumber of expected instances of the PDSCH transmission, where the ruleis based at least one of the PDSCH configuration or the SPSconfiguration. The UE may identify a configuration of the firstaggregation factor from the SPS configuration and may identify a numberof repetitions of the PDSCH transmission at 645 corresponding to a valueof the first aggregation factor. In some examples, two or more instances(e.g., repetitions) of the PDSCH transmission are received based on theidentified number of repetitions at 645. In some cases, the UE mayidentify the number of repetitions of the PDSCH transmissioncorresponding to the first aggregation factor, where two or moreinstances of the PDSCH transmission are received based on the identifiednumber of repetitions.

At 630, the UE may determine that the SPS configuration in 620 does notinclude the configuration of the first aggregation factor. The UE mayidentify a configuration of a second aggregation factor from the PDSCHconfiguration based on the exclusion of the first aggregation factor inthe SPS configuration. The UE may identify a number of repetitions ofthe PDSCH transmission corresponding to a value of the secondaggregation factor at 635, where two or more instances (e.g.,repetitions) of the PDSCH transmission are received based on theidentified number of repetitions at 645.

At 640, the UE may determine that the SPS configuration excludes aconfiguration of a first aggregation factor. The UE may also determine,based on the SPS configuration excluding the configuration of the firstaggregation factor, that the PDSCH configuration also excludes aconfiguration of a second aggregation factor. The UE may furtherdetermine that the number of expected instances of the PDSCHtransmission is equal to one the SPS configuration excluding theconfiguration of the first aggregation factor and the PDSCHconfiguration excluding the configuration of the second aggregationfactor.

The UE may determine that a single instance of the PDSCH transmission isreceived based on the number of expected instances at 640. For example,the UE may determine that the number of expected instances of the PDSCHtransmission is equal to one based on the SPS configuration excludingthe configuration of the first aggregation factor and the PDSCHconfiguration excluding the configuration of the second aggregationfactor, wherein a single instance of the PDSCH transmission is receivedbased on the number of expected instances.

FIG. 7 illustrates an example of a flow chart 700 that supportstechniques for dynamically aggregating a physical downlink sharedchannel for SPS in accordance with aspects of the present disclosure. Insome examples, flow chart 700 may implement aspects of wirelesscommunications system 100. In some examples, flow chart 700 may beimplemented by a UE, such as a UE described with reference to FIGS. 1and 2 . However, it is also noted that aspects of the flow chart 700 maybe used by a base station, such as a base station 105 described withreference to FIGS. 1 and 2 , when determining a number of repetitionsfor transmitting PDSCH.

At 705, the UE may receive an SPS configuration from a set of one ormore SPS configurations.

At 710, the UE may identify a repetition scheme configuration based onthe received SPS configuration. In some cases, the UE may receive aPDSCH configuration identifying the repetition scheme configurationbased on the received PDSCH configuration, where the SPS configurationexcludes the repetition scheme configuration. In some examples, therepetition scheme may include a first frequency division multiplexingscheme, a second frequency division multiplexing scheme, and a timedivision multiplexing scheme.

At 715, the UE may receive DCI associated with a PDSCH transmission forthe SPS configuration and may identify, within the DCI, an indication ofa number of TCI states. In some cases, the number of TCI states includestwo TCI states. In some cases, the DCI may a cyclic redundancy checkthat is scrambled by a configured scheduling radio network temporaryidentifier, the DCI containing a new data indicator equal to zero, andwherein the DCI activates the SPS configuration.

At 720, the UE may identify whether the SPS configuration includes anaggregation factor. In some examples, the UE may identify that the SPSconfiguration includes a configuration of a first aggregation factor.

In some examples, such as at 725, the UE may identify a number ofconsecutive slot time periods that correspond to a value of the firstaggregation factor (e.g., the UE may use the value of the aggregationfactor to determine a number of PDSCH repetitions).

In some other examples, such as at 730, the UE may determine that theSPS configuration excludes a configuration of a first aggregation factorand the UE may identify, based on the SPS configuration excluding theconfiguration of the first aggregation factor, a configuration of asecond aggregation factor from the PDSCH configuration. The UE mayidentify a number of consecutive slot time periods that corresponds to avalue of the second aggregation factor. In some other cases, the UE maydetermine that the SPS configuration does not include the aggregationfactor at 730, and may determine the number of repetitions to be 1.

At 735, the UE may receive one or more repetitions of the PDSCHtransmission based on the repetition scheme configuration, or the numberof transmission configuration indicator states, or a combinationthereof. The UE may receive the one or more repetitions of the PDSCHtransmission within a same slot time period, the slot time periodoccurring within each SPS time period of a plurality of SPS timeperiods. In some other examples, the UE may receive the one or morerepetitions of the PDSCH transmission within a plurality of consecutiveslot time periods occurring within each SPS time period, each slot timeperiod of the plurality of consecutive slot time periods comprising tworepetitions of the PDSCH transmission.

FIG. 8 shows a block diagram 800 of a device 805 that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure. The device 805 may be an exampleof aspects of a UE 115 as described herein. The device 805 may include areceiver 810, a communications manager 815, and a transmitter 820. Thedevice 805 may also include a processor. Each of these components may bein communication with one another (e.g., via one or more buses).

The receiver 810 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to techniquesfor dynamically aggregating a PDSCH for SPS, etc.). Information may bepassed on to other components of the device 805. The receiver 810 may bean example of aspects of the transceiver 1120 described with referenceto FIG. 11 . The receiver 810 may utilize a single antenna or a set ofantennas.

The communications manager 815 may receive a PDSCH configuration and anSPS configuration from a set of one or more SPS configurations, receiveDCI associated with a PDSCH transmission for the SPS configuration,determine, based on a rule, a repetition number for a number of expectedinstances of the PDSCH transmission, where the rule is based on apriority between a TDRA entry indicated by the DCI and at least one ofthe PDSCH configuration or the SPS configuration, and receive, withineach SPS time period of a set of SPS time periods, one or more instancesof the PDSCH transmission in accordance with the repetition number.

The communications manager 815 may also receive an SPS configurationfrom a set of one or more SPS configurations, identify a repetitionscheme configuration, receive DCI associated with a PDSCH transmissionfor the SPS configuration, identify, within the DCI, an indication of aset of TCI states, and receive one or more repetitions of the PDSCHtransmission based on the repetition scheme configuration, or the set ofTCI states, or a combination thereof. The communications manager 815 maybe an example of aspects of the communications manager 1110 describedherein.

The communications manager 815, or its sub-components, may beimplemented in hardware, code (e.g., software or firmware) executed by aprocessor, or any combination thereof. If implemented in code executedby a processor, the functions of the communications manager 815, or itssub-components may be executed by a general-purpose processor, a digitalsignal processor (DSP), an application-specific integrated circuit(ASIC), a field-programmable gate array (FPGA) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed in the present disclosure.

The communications manager 815, or its sub-components, may be physicallylocated at various positions, including being distributed such thatportions of functions are implemented at different physical locations byone or more physical components. In some examples, the communicationsmanager 815, or its sub-components, may be a separate and distinctcomponent in accordance with various aspects of the present disclosure.In some examples, the communications manager 815, or its sub-components,may be combined with one or more other hardware components, includingbut not limited to an input/output (I/O) component, a transceiver, anetwork server, another computing device, one or more other componentsdescribed in the present disclosure, or a combination thereof inaccordance with various aspects of the present disclosure.

The transmitter 820 may transmit signals generated by other componentsof the device 805. In some examples, the transmitter 820 may becollocated with a receiver 810 in a transceiver module. For example, thetransmitter 820 may be an example of aspects of the transceiver 1120described with reference to FIG. 11 . The transmitter 820 may utilize asingle antenna or a set of antennas.

FIG. 9 shows a block diagram 900 of a device 905 that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure. The device 905 may be an exampleof aspects of a device 805, or a UE 115 as described herein. The device905 may include a receiver 910, a communications manager 915, and atransmitter 945. The device 905 may also include a processor. Each ofthese components may be in communication with one another (e.g., via oneor more buses).

The receiver 910 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to techniquesfor dynamically aggregating a PDSCH for SPS, etc.). Information may bepassed on to other components of the device 905. The receiver 910 may bean example of aspects of the transceiver 1120 described with referenceto FIG. 11 . The receiver 910 may utilize a single antenna or a set ofantennas.

The communications manager 915 may be an example of aspects of thecommunications manager 815 as described herein. The communicationsmanager 915 may include a configuration manager 920, an SPS manager 925,a repetition manager 930, a PDSCH component 935, and a TCI state manager940. The communications manager 915 may be an example of aspects of thecommunications manager 1110 described herein.

The configuration manager 920 may receive a PDSCH configuration and anSPS configuration from a set of one or more SPS configurations. In someexamples, the configuration manager 920 may identify a repetition schemeconfiguration. The SPS manager 925 may receive DCI associated with aPDSCH transmission for the SPS configuration.

The repetition manager 930 may determine, based on a rule, a repetitionnumber for a number of expected instances of the PDSCH transmission,where the rule is based on a priority between a TDRA entry indicated bythe DCI and at least one of the PDSCH configuration or the SPSconfiguration.

The PDSCH component 935 may receive, within each SPS time period of aset of SPS time periods, one or more instances of the PDSCH transmissionin accordance with the repetition number. In some examples, the PDSCHcomponent 935 may receive one or more repetitions of the PDSCHtransmission based on the repetition scheme configuration, or the set ofTCI states, or a combination thereof. The TCI state manager 940 mayidentify, within the DCI, an indication of a set of TCI states.

The transmitter 945 may transmit signals generated by other componentsof the device 905. In some examples, the transmitter 945 may becollocated with a receiver 910 in a transceiver module. For example, thetransmitter 945 may be an example of aspects of the transceiver 1120described with reference to FIG. 11 . The transmitter 945 may utilize asingle antenna or a set of antennas.

In some examples, communications manager 915 may be implemented as anintegrated circuit or chipset for a mobile device modem, and thereceiver 910 and transmitter 945 may be implemented as analog components(e.g., amplifiers, filters, antennas, etc.) coupled with the mobiledevice modem to enable wireless transmission and reception.

The communications manager 915 as described herein may be implemented torealize one or more potential advantages. Various implementations mayenable communications manager 915 to reduce overall signaling overheadby implementing communications involving SPS. Based on implementing thetechniques for dynamically aggregating a PDSCH for SPS as describedherein, one or more processors of the device 905 (e.g., processor(s)controlling or incorporated with one or more of receiver 910,communications manager 915, and transmitter 945) may reduce thecomplexity in determining how many repetitions may be received at thedevice 905. In addition, the techniques described herein may increaseoverall communications efficiency and reduce communications latency atthe device 905.

FIG. 10 shows a block diagram 1000 of a communications manager 1005 thatsupports techniques for dynamically aggregating a PDSCH for SPS inaccordance with aspects of the present disclosure. The communicationsmanager 1005 may be an example of aspects of a communications manager815, a communications manager 915, or a communications manager 1110described herein. The communications manager 1005 may include aconfiguration manager 1010, an SPS manager 1015, a repetition manager1020, a PDSCH component 1025, a TDRA component 1030, and a TCI statemanager 1035. Each of these modules may communicate, directly orindirectly, with one another (e.g., via one or more buses).

The configuration manager 1010 may receive a PDSCH configuration and anSPS configuration from a set of one or more SPS configurations. In someexamples, the configuration manager 1010 may receive an SPSconfiguration from a set of one or more SPS configurations. In someexamples, the configuration manager 1010 may identify a repetitionscheme configuration. In some examples, the configuration manager 1010may identify, based on the TDRA entry excluding the repetition number, aconfiguration of a first aggregation factor from the SPS configuration.In some examples, the configuration manager 1010 may determine, based ona TDRA entry excluding a repetition number, that the SPS configurationexcludes a configuration of a first aggregation factor.

In some examples, the configuration manager 1010 may identify, based onthe SPS configuration excluding the configuration of a first aggregationfactor, a configuration of a second aggregation factor from the PDSCHconfiguration. In other examples, the configuration manager 1010 maydetermine, based on the SPS configuration excluding the configuration ofthe first aggregation factor, that the PDSCH configuration excludes aconfiguration of a second aggregation factor.

In some examples, the configuration manager 1010 may identify, from theSPS configuration, a configuration of a first aggregation factor.Additionally or alternatively, the configuration manager 1010 maydetermine that the SPS configuration excludes a configuration of thefirst aggregation factor. In some examples, the configuration manager1010 may identify, from the PDSCH configuration, a configuration of afirst aggregation factor. Additionally or alternatively, theconfiguration manager 1010 may determine that the PDSCH configurationexcludes a configuration of a first aggregation factor or thesemi-persistent scheduling configuration excludes a configuration of asecond aggregation factor, or both. In some examples, the configurationmanager 1010 may identify a repetition scheme configuration based on thereceived SPS configuration. In some examples, the configuration manager1010 may identify the repetition scheme configuration based on thereceived PDSCH configuration, where the SPS configuration excludes therepetition scheme configuration.

In some cases, the PDSCH configuration and the SPS configuration arereceived via RRC signaling. In some cases, the repetition scheme mayinclude a first frequency division multiplexing scheme (e.g.,FDMSchemeA), a second frequency division multiplexing scheme (e.g.,FDMSchemeB), or a time division multiplexing scheme (e.g., TDMSchemeA),or the like.

The SPS manager 1015 may receive DCI associated with a PDSCHtransmission for the SPS configuration. In some cases, the DCI has acyclic redundancy check that is scrambled by a configured schedulingradio network temporary identifier, the DCI including a new dataindicator equal to zero, and where the DCI activates the SPSconfiguration. In some cases, the DCI has a cyclic redundancy check thatis scrambled by a configured scheduling radio network temporaryidentifier, the DCI including a new data indicator equal to one, andwhere the PDSCH transmission includes a retransmission ofsemi-persistently scheduled PDSCH scheduled by the DCI. In some cases,the DCI has a DCI format 1_1. In other examples, the DCI has a DCIformat 1_2. In some cases, the DCI has a cyclic redundancy check that isscrambled by a configured scheduling radio network temporary identifier,the DCI including a new data indicator equal to zero, and where the DCIactivates the SPS configuration.

The repetition manager 1020 may determine, based on a rule, a repetitionnumber for a number of expected instances of the PDSCH transmission,where the rule is based on a priority between a TDRA entry indicated bythe DCI and at least one of the PDSCH configuration or the SPSconfiguration. In some examples, the repetition manager 1020 mayidentify a number of repetitions of the PDSCH transmission based atleast in part on a value of the repetition number, where two or moreinstances of the PDSCH transmission are received based on the identifiednumber of repetitions.

In some examples, the repetition manager 1020 may identify a number ofrepetitions of the PDSCH transmission corresponding to a value of thefirst aggregation factor, where two or more instances of the PDSCHtransmission are received based on the identified number of repetitions.In some examples, the repetition manager 1020 may identify a number ofrepetitions of the PDSCH transmission corresponding to a value of thesecond aggregation factor, where two or more instances of the PDSCHtransmission are received based on the identified number of repetitions.

In some examples, the repetition manager 1020 may receive the one ormore repetitions of the PDSCH transmission within a same slot timeperiod, the slot time period occurring within each SPS time period of aset of SPS time periods. In some examples, the repetition manager 1020may receive the one or more repetitions of the PDSCH transmission withina set of consecutive slot time periods occurring within each SPS timeperiod of a set of SPS time periods, each slot time period of the set ofconsecutive slot time periods including two repetitions of the PDSCHtransmission. In some cases, the number of repetitions of the PDSCHtransmission are within a time period that is less than or equal to theSPS time period.

The PDSCH component 1025 may receive, within each SPS time period of aset of SPS time periods, one or more instances of the PDSCH transmissionin accordance with the repetition number. In some examples, the PDSCHcomponent 1025 may receive one or more repetitions of the PDSCHtransmission based on the repetition scheme configuration, or the set ofTCI states, or a combination thereof.

In some examples, the PDSCH component 1025 may determine that the numberof expected instances of the PDSCH transmission is equal to one based onthe TDRA entry excluding the repetition number, where a single instanceof the PDSCH transmission is received based on the number of expectedinstances. In some examples, the PDSCH component 1025 may determine thatthe number of expected instances of the PDSCH transmission is equal toone based on the SPS configuration excluding the configuration of thefirst aggregation factor and the PDSCH configuration excluding theconfiguration of the second aggregation factor, where a single instanceof the PDSCH transmission is received based on the number of expectedinstances. In some examples, the PDSCH component 1025 may determine thatthe number of expected instances of the PDSCH transmission is equal toone based on the PDSCH configuration excluding the configuration of thefirst aggregation factor, where a single instance of the PDSCHtransmission is received based on the number of expected instances.

Additionally or alternatively, the PDSCH component 1025 may determinethat the number of expected instances of the PDSCH transmission is equalto one based on the TDRA entry excluding the repetition number, the SPSconfiguration excluding the configuration of the first aggregationfactor, and the PDSCH configuration excluding the configuration of thesecond aggregation factor, where a single instance of the PDSCHtransmission is received based on the number of expected instances.

In some examples, the PDSCH component 1025 may identify a number of theset of consecutive slot time periods that corresponds to a value of thefirst aggregation factor. In other examples, the PDSCH component 1025may identify a number of the set of consecutive slot time periods thatcorresponds to a value of the second aggregation factor. In some cases,the one or more instances of the PDSCH transmission are received in adifferent slot time period of a set of consecutive slot time periods.

The TCI state manager 1035 may identify, within the DCI, an indicationof a set of TCI states. In some cases, the set of TCI states includestwo TCI states. The TDRA component 1030 may determine that the TDRAentry indicated by the DCI includes the repetition number. In someexamples, the TDRA component 1030 may determine that the TDRA entryindicated by the DCI excludes the repetition number.

In some examples, the TDRA component 1030 may receive a configuration ofthe TDRA table via RRC signaling. In some cases, the TDRA entry is froma TDRA table that includes a set of TDRA entries, and where at least oneTDRA entry of the set of TDRA entries includes the repetition number. Insome cases, the repetition number is indicated by at least one column ofthe TDRA table.

FIG. 11 shows a diagram of a system 1100 including a device 1105 thatsupports techniques for dynamically aggregating a PDSCH for SPS inaccordance with aspects of the present disclosure. The device 1105 maybe an example of or include the components of device 805, device 905, ora UE 115 as described herein. The device 1105 may include components forbi-directional voice and data communications including components fortransmitting and receiving communications, including a communicationsmanager 1110, an I/O controller 1115, a transceiver 1120, an antenna1125, memory 1130, and a processor 1140. These components may be inelectronic communication via one or more buses (e.g., bus 1145).

The communications manager 1110 may receive a PDSCH configuration and anSPS configuration from a set of one or more SPS configurations, receiveDCI associated with a PDSCH transmission for the SPS configuration,determine, based on a rule, a repetition number for a number of expectedinstances of the PDSCH transmission, where the rule is based on apriority between a TDRA entry indicated by the DCI and at least one ofthe PDSCH configuration or the SPS configuration, and receive, withineach SPS time period of a set of SPS time periods, one or more instancesof the PDSCH transmission in accordance with the repetition number.

The communications manager 1110 may also receive an SPS configurationfrom a set of one or more SPS configurations, identify a repetitionscheme configuration, receive DCI associated with a PDSCH transmissionfor the SPS configuration, identify, within the DCI, an indication of aset of TCI states, and receive one or more repetitions of the PDSCHtransmission based on the repetition scheme configuration, or the set ofTCI states, or a combination thereof.

The I/O controller 1115 may manage input and output signals for thedevice 1105. The I/O controller 1115 may also manage peripherals notintegrated into the device 1105. In some cases, the I/O controller 1115may represent a physical connection or port to an external peripheral.In some cases, the I/O controller 1115 may utilize an operating systemsuch as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, oranother known operating system. In other cases, the I/O controller 1115may represent or interact with a modem, a keyboard, a mouse, atouchscreen, or a similar device. In some cases, the I/O controller 1115may be implemented as part of a processor. In some cases, a user mayinteract with the device 1105 via the I/O controller 1115 or viahardware components controlled by the I/O controller 1115.

The transceiver 1120 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described herein. For example, thetransceiver 1120 may represent a wireless transceiver and maycommunicate bi-directionally with another wireless transceiver. Thetransceiver 1120 may also include a modem to modulate the packets andprovide the modulated packets to the antennas for transmission, and todemodulate packets received from the antennas. In some cases, thewireless device may include a single antenna 1125. However, in somecases the device may have more than one antenna 1125, which may becapable of concurrently transmitting or receiving multiple wirelesstransmissions.

The memory 1130 may include random-access memory (RAM) and read-onlymemory (ROM). The memory 1130 may store computer-readable,computer-executable code 1135 including instructions that, whenexecuted, cause the processor to perform various functions describedherein. In some cases, the memory 1130 may contain, among other things,a basic input/output system (BIOS) which may control basic hardware orsoftware operation such as the interaction with peripheral components ordevices.

The processor 1140 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 1140 may be configured to operate a memoryarray using a memory controller. In other cases, a memory controller maybe integrated into the processor 1140. The processor 1140 may beconfigured to execute computer-readable instructions stored in a memory(e.g., the memory 1130) to cause the device 1105 to perform variousfunctions (e.g., functions or tasks supporting techniques fordynamically aggregating a PDSCH for SPS).

The code 1135 may include instructions to implement aspects of thepresent disclosure, including instructions to support wirelesscommunications. The code 1135 may be stored in a non-transitorycomputer-readable medium such as system memory or other type of memory.In some cases, the code 1135 may not be directly executable by theprocessor 1140 but may cause a computer (e.g., when compiled andexecuted) to perform functions described herein.

FIG. 12 shows a block diagram 1200 of a device 1205 that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure. The device 1205 may be anexample of aspects of a base station 105 as described herein. The device1205 may include a receiver 1210, a communications manager 1215, and atransmitter 1220. The device 1205 may also include a processor. Each ofthese components may be in communication with one another (e.g., via oneor more buses).

The receiver 1210 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to techniquesfor dynamically aggregating a PDSCH for SPS, etc.). Information may bepassed on to other components of the device 1205. The receiver 1210 maybe an example of aspects of the transceiver 1520 described withreference to FIG. 15 . The receiver 1210 may utilize a single antenna ora set of antennas.

The communications manager 1215 may transmit, to a UE, a PDSCHconfiguration and an SPS configuration from a set of one or more SPSconfigurations, transmit, to the UE, DCI associated with a PDSCHtransmission for the SPS configuration, determine, based on a rule, arepetition number for a number of expected instances of the PDSCHtransmission, where the rule is based on a priority between a TDRA entryindicated by the DCI and at least one of the PDSCH configuration or theSPS configuration, and transmit, within each SPS time period of a set ofSPS time periods, one or more instances of the PDSCH transmission inaccordance with the repetition number. The communications manager 1215may also transmit, to a UE, an SPS configuration from a set of one ormore SPS configurations, configure a repetition scheme for the UE,transmit, to the UE, DCI associated with a PDSCH transmission for theSPS configuration, configure, within the DCI, an indication of a set ofTCI states, and transmit one or more repetitions of the PDSCHtransmission to the UE based on the configured repetition scheme, or theset of TCI states, or a combination thereof. The communications manager1215 may be an example of aspects of the communications manager 1510described herein.

The communications manager 1215, or its sub-components, may beimplemented in hardware, code (e.g., software or firmware) executed by aprocessor, or any combination thereof. If implemented in code executedby a processor, the functions of the communications manager 1215, or itssub-components may be executed by a general-purpose processor, a DSP, anapplication-specific integrated circuit (ASIC), an FPGA or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described in the present disclosure.

The communications manager 1215, or its sub-components, may bephysically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations by one or more physical components. In some examples, thecommunications manager 1215, or its sub-components, may be a separateand distinct component in accordance with various aspects of the presentdisclosure. In some examples, the communications manager 1215, or itssub-components, may be combined with one or more other hardwarecomponents, including but not limited to an input/output (I/O)component, a transceiver, a network server, another computing device,one or more other components described in the present disclosure, or acombination thereof in accordance with various aspects of the presentdisclosure.

The transmitter 1220 may transmit signals generated by other componentsof the device 1205. In some examples, the transmitter 1220 may becollocated with a receiver 1210 in a transceiver module. For example,the transmitter 1220 may be an example of aspects of the transceiver1520 described with reference to FIG. 15 . The transmitter 1220 mayutilize a single antenna or a set of antennas.

FIG. 13 shows a block diagram 1300 of a device 1305 that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure. The device 1305 may be anexample of aspects of a device 1205, or a base station 105 as describedherein. The device 1305 may include a receiver 1310, a communicationsmanager 1315, and a transmitter 1350. The device 1305 may also include aprocessor. Each of these components may be in communication with oneanother (e.g., via one or more buses).

The receiver 1310 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to techniquesfor dynamically aggregating a PDSCH for SPS, etc.). Information may bepassed on to other components of the device 1305. The receiver 1310 maybe an example of aspects of the transceiver 1520 described withreference to FIG. 15 . The receiver 1310 may utilize a single antenna ora set of antennas.

The communications manager 1315 may be an example of aspects of thecommunications manager 1215 as described herein. The communicationsmanager 1315 may include a configuration component 1320, a DCI component1325, a repetition configuration manager 1330, an SPS transmissioncomponent 1335, and TCI configuration component 1340. The communicationsmanager 1315 may be an example of aspects of the communications manager1510 described herein.

The configuration component 1320 may transmit, to a UE, a PDSCHconfiguration and an SPS configuration from a set of one or more SPSconfigurations. In some cases, the configuration component 1320 mayconfigure a repetition scheme for the UE.

The DCI component 1325 may transmit, to the UE, DCI associated with aPDSCH transmission for the SPS configuration. The repetitionconfiguration manager 1330 may determine, based on a rule, a repetitionnumber for a number of expected instances of the PDSCH transmission,where the rule is based on a priority between a TDRA entry indicated bythe DCI and at least one of the PDSCH configuration or the SPSconfiguration.

The SPS transmission component 1335 may transmit, within each SPS timeperiod of a set of SPS time periods, one or more instances of the PDSCHtransmission in accordance with the repetition number. The SPStransmission component 1335 may transmit one or more repetitions of thePDSCH transmission to the UE based on the configured repetition scheme,or the set of TCI states, or a combination thereof. The TCIconfiguration component 1340 may configure, within the DCI, anindication of a set of TCI states.

The transmitter 1350 may transmit signals generated by other componentsof the device 1305. In some examples, the transmitter 1350 may becollocated with a receiver 1310 in a transceiver module. For example,the transmitter 1350 may be an example of aspects of the transceiver1520 described with reference to FIG. 15 . The transmitter 1350 mayutilize a single antenna or a set of antennas.

FIG. 14 shows a block diagram 1400 of a communications manager 1405 thatsupports techniques for dynamically aggregating a PDSCH for SPS inaccordance with aspects of the present disclosure. The communicationsmanager 1405 may be an example of aspects of a communications manager1215, a communications manager 1315, or a communications manager 1510described herein. The communications manager 1405 may include aconfiguration component 1410, a DCI component 1415, a repetitionconfiguration manager 1420, an SPS transmission component 1425, an SPSmanager 1430, and a TCI configuration component 1435. Each of thesemodules may communicate, directly or indirectly, with one another (e.g.,via one or more buses).

The configuration component 1410 may transmit, to a UE, a PDSCHconfiguration and an SPS configuration from a set of one or more SPSconfigurations. In some examples, the configuration component 1410 mayconfigure a first aggregation factor as part of the PDSCH configuration.In some examples, the configuration component 1410 may configure a firstaggregation factor as part of the SPS configuration, where a number of aset of consecutive slot time periods corresponds to a value of the firstaggregation factor. In some examples, the configuration component 1410may configure, based on the SPS configuration excluding a configurationof a first aggregation factor, a second aggregation factor as part of aPDSCH configuration.

In some examples, the configuration component 1410 may transmit thePDSCH configuration to the UE, where a number of the set of consecutiveslot time periods corresponds to a value of the second aggregationfactor. In some examples, the configuration component 1410 may transmitan indication of the configured repetition scheme as part of the SPSconfiguration. In some examples, the configuration component 1410 maytransmit, to the UE, a PDSCH configuration including an indication ofthe configured repetition scheme, where the SPS configuration excludesthe indication of the configured repetition scheme. In some cases, therepetition scheme may include a first frequency division multiplexingscheme, a second frequency division multiplexing scheme, or a timedivision multiplexing scheme. The configuration component 1410 mayconfigure a repetition scheme for the UE.

The DCI component 1415 may transmit, to the UE, DCI associated with aPDSCH transmission for the SPS configuration. In some cases, the DCIincludes a new data indicator equal to zero, and where the DCI activatesthe SPS configuration. In some cases, the DCI includes a new dataindicator equal to one, and where the PDSCH transmission includes aretransmission of semi-persistently scheduled PDSCH scheduled by theDCI. In some cases, the DCI has a DCI format 1_1. Additionally oralternatively, the DCI has a DCI format 1_2. In some cases, the DCI hasa cyclic redundancy check that is scrambled by a configured schedulingradio network temporary identifier, the DCI including a NDI equal tozero, and where the DCI activates the SPS configuration.

The repetition configuration manager 1420 may determine, based on arule, a repetition number for a number of expected instances of thePDSCH transmission, where the rule is based on a priority between a TDRAentry indicated by the DCI and at least one of the PDSCH configurationor the SPS configuration. In some examples, the repetition configurationmanager 1420 may determine that the TDRA entry indicated by the DCIincludes the repetition number. In some examples, the repetitionconfiguration manager 1420 may determine that the TDRA entry indicatedby the DCI excludes the repetition number.

In some examples, determining that the TDRA entry indicated by the DCIexcludes the repetition number, where the SPS configuration includes aconfiguration of a first aggregation factor.

In some examples, the repetition configuration manager 1420 maydetermine that the TDRA entry indicated by the DCI excludes therepetition number, where the SPS configuration excludes a configurationof a first aggregation factor and the PDSCH configuration includes aconfiguration of a second aggregation factor. In some examples, therepetition configuration manager 1420 may determine that the TDRA entryindicated by the DCI excludes the repetition number, where the SPSconfiguration excludes a configuration of a first aggregation factor andthe PDSCH configuration excludes a configuration of a second aggregationfactor.

In some examples, the repetition configuration manager 1420 mayconfigure a first aggregation factor as part of the SPS configuration.In some examples, determining that the SPS configuration excludes aconfiguration of a first aggregation factor, where the PDSCHconfiguration includes a configuration of a second aggregation factor.In some examples, the repetition configuration manager 1420 maytransmit, to the UE, a configuration of the TDRA table via radioresource control signaling.

In some cases, the TDRA entry is an entry from a TDRA table thatincludes a set of TDRA entries, and where at least one TDRA entry of theset of TDRA entries includes the repetition number. In some cases, therepetition number is indicated by at least one column of the TDRA table.

The SPS transmission component 1425 may transmit, within each SPS timeperiod of a set of SPS time periods, one or more instances of the PDSCHtransmission in accordance with the repetition number. In some examples,the SPS transmission component 1425 may transmit one or more repetitionsof the PDSCH transmission to the UE based on the configured repetitionscheme, or the set of TCI states, or a combination thereof.

In some examples, the SPS transmission component 1425 may identify anumber of repetitions of the PDSCH transmission based at least in parton a value of the repetition number, where two or more instances of thePDSCH transmission are transmitted based on the identified number ofrepetitions. In some examples, the SPS transmission component 1425 maydetermine that the number of expected instances of the PDSCHtransmission is equal to one based on the TDRA entry excluding therepetition number, where a single instance of the PDSCH transmission istransmitted based on the number of expected instances. Additionally oralternatively, the SPS transmission component 1425 may identify a numberof repetitions of the PDSCH transmission corresponding to a value of thefirst aggregation factor, where two or more instances of the PDSCHtransmission are transmitted based on the identified number ofrepetitions.

In some examples, the SPS transmission component 1425 may identify anumber of repetitions of the PDSCH transmission corresponding to a valueof the second aggregation factor, where two or more instances of thePDSCH transmission are transmitted based on the identified number ofrepetitions. In some examples, the SPS transmission component 1425 maydetermine that the number of expected instances of the PDSCHtransmission is equal to one based on the TDRA entry excluding therepetition number, the SPS configuration excluding a configuration ofthe first aggregation factor, and the PDSCH configuration excluding aconfiguration of the second aggregation factor, where a single instanceof the PDSCH transmission is transmitted based on the number of expectedinstances.

In some examples, the SPS transmission component 1425 may determine thatthe number of expected instances of the PDSCH transmission is equal toone based on the SPS configuration excluding a configuration of a firstaggregation factor and the PDSCH configuration excluding a configurationof a second aggregation factor, where a single instance of the PDSCHtransmission is transmitted based on the number of expected instances.In some cases, the SPS transmission component 1425 may determine thatthe number of expected instances of the PDSCH transmission is equal toone based on the PDSCH configuration excluding a configuration of afirst aggregation factor, where a single instance of the PDSCHtransmission is transmitted based on the number of expected instances.

In some examples, the SPS transmission component 1425 may transmit theone or more repetitions of the PDSCH transmission within a same slottime period, the slot time period occurring within each SPS time periodof a set of SPS time periods. In some examples, the SPS transmissioncomponent 1425 may transmit the one or more repetitions of the PDSCHtransmission within a set of consecutive slot time periods occurringwithin each SPS time period of a set of SPS time periods, each slot timeperiod of the set of consecutive slot time periods including tworepetitions of the PDSCH transmission. In some cases, the number ofrepetitions of the PDSCH transmission are within a time period that isless than or equal to the SPS time period.

TCI configuration component 1435 may configure, within the DCI, anindication of a set of TCI states. In some cases, the set of TCI statesincludes two TCI states. In some cases, the one or more instances of thePDSCH transmission are received in a different slot time period of a setof consecutive slot time periods.

FIG. 15 shows a diagram of a system 1500 including a device 1505 thatsupports techniques for dynamically aggregating a PDSCH for SPS inaccordance with aspects of the present disclosure. The device 1505 maybe an example of or include the components of device 1205, device 1305,or a base station 105 as described herein. The device 1505 may includecomponents for bi-directional voice and data communications includingcomponents for transmitting and receiving communications, including acommunications manager 1510, a network communications manager 1515, atransceiver 1520, an antenna 1525, memory 1530, a processor 1540, and aninter-station communications manager 1545. These components may be inelectronic communication via one or more buses (e.g., bus 1550).

The communications manager 1510 may transmit, to a UE, a PDSCHconfiguration and an SPS configuration from a set of one or more SPSconfigurations, transmit, to the UE, DCI associated with a PDSCHtransmission for the SPS configuration, determine, based on a rule, arepetition number for a number of expected instances of the PDSCHtransmission, where the rule is based on a priority between a TDRA entryindicated by the DCI and at least one of the PDSCH configuration or theSPS configuration, and transmit, within each SPS time period of a set ofSPS time periods, one or more instances of the PDSCH transmission inaccordance with the repetition number. The communications manager 1510may also transmit, to a UE, an SPS configuration from a set of one ormore SPS configurations, configure a repetition scheme for the UE,transmit, to the UE, DCI associated with a PDSCH transmission for theSPS configuration, configure, within the DCI, an indication of a set ofTCI states, and transmit one or more repetitions of the PDSCHtransmission to the UE based on the configured repetition scheme, or theset of TCI states, or a combination thereof.

The network communications manager 1515 may manage communications withthe core network (e.g., via one or more wired backhaul links). Forexample, the network communications manager 1515 may manage the transferof data communications for client devices, such as one or more UEs 115.

The transceiver 1520 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described herein. For example, thetransceiver 1520 may represent a wireless transceiver and maycommunicate bi-directionally with another wireless transceiver. Thetransceiver 1520 may also include a modem to modulate the packets andprovide the modulated packets to the antennas for transmission, and todemodulate packets received from the antennas. In some cases, thewireless device may include a single antenna 1525. However, in somecases the device may have more than one antenna 1525, which may becapable of concurrently transmitting or receiving multiple wirelesstransmissions.

The memory 1530 may include RAM, ROM, or a combination thereof. Thememory 1530 may store computer-readable code 1535 including instructionsthat, when executed by a processor (e.g., the processor 1540) cause thedevice to perform various functions described herein. In some cases, thememory 1530 may contain, among other things, a BIOS which may controlbasic hardware or software operation such as the interaction withperipheral components or devices.

The processor 1540 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 1540 may be configured to operate a memoryarray using a memory controller. In some cases, a memory controller maybe integrated into processor 1540. The processor 1540 may be configuredto execute computer-readable instructions stored in a memory (e.g., thememory 1530) to cause the device 1505 to perform various functions(e.g., functions or tasks supporting techniques for dynamicallyaggregating a PDSCH for SPS).

The inter-station communications manager 1545 may manage communicationswith other base station 105, and may include a controller or schedulerfor controlling communications with UEs 115 in cooperation with otherbase stations 105. For example, the inter-station communications manager1545 may coordinate scheduling for transmissions to UEs 115 for variousinterference mitigation techniques such as beamforming or jointtransmission. In some examples, the inter-station communications manager1545 may provide an X2 interface within an LTE/LTE-A wirelesscommunication network technology to provide communication between basestations 105.

The code 1535 may include instructions to implement aspects of thepresent disclosure, including instructions to support wirelesscommunications. The code 1535 may be stored in a non-transitorycomputer-readable medium such as system memory or other type of memory.In some cases, the code 1535 may not be directly executable by theprocessor 1540 but may cause a computer (e.g., when compiled andexecuted) to perform functions described herein.

FIG. 16 shows a flowchart illustrating a method 1600 that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure. The operations of method 1600may be implemented by a UE 115 or its components as described herein.For example, the operations of method 1600 may be performed by acommunications manager as described with reference to FIGS. 8 through 11. In some examples, a UE may execute a set of instructions to controlthe functional elements of the UE to perform the functions describedherein. Additionally or alternatively, a UE may perform aspects of thefunctions described herein using special-purpose hardware.

At 1605, the UE may receive a PDSCH configuration and an SPSconfiguration from a set of one or more SPS configurations. Theoperations of 1605 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1605 may beperformed by a configuration manager as described with reference toFIGS. 8 through 11 .

At 1610, the UE may receive DCI associated with a PDSCH transmission forthe SPS configuration. The operations of 1610 may be performed accordingto the methods described herein. In some examples, aspects of theoperations of 1610 may be performed by an SPS manager as described withreference to FIGS. 8 through 11 .

At 1615, the UE may determine, based on a rule, a repetition number fora number of expected instances of the PDSCH transmission, where the ruleis based on a priority between a TDRA entry indicated by the DCI and atleast one of the PDSCH configuration or the SPS configuration. Theoperations of 1615 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1615 may beperformed by a repetition manager as described with reference to FIGS. 8through 11 .

At 1620, the UE may receive, within each SPS time period of a set of SPStime periods, one or more instances of the PDSCH transmission inaccordance with the repetition number. The operations of 1620 may beperformed according to the methods described herein. In some examples,aspects of the operations of 1620 may be performed by a PDSCH componentas described with reference to FIGS. 8 through 11 .

FIG. 17 shows a flowchart illustrating a method 1700 that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure. The operations of method 1700may be implemented by a UE 115 or its components as described herein.For example, the operations of method 1700 may be performed by acommunications manager as described with reference to FIGS. 8 through 11. In some examples, a UE may execute a set of instructions to controlthe functional elements of the UE to perform the functions describedherein. Additionally or alternatively, a UE may perform aspects of thefunctions described herein using special-purpose hardware.

At 1705, the UE may receive an SPS configuration from a set of one ormore SPS configurations. The operations of 1705 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1705 may be performed by a configuration manager asdescribed with reference to FIGS. 8 through 11 .

At 1710, the UE may identify a repetition scheme configuration. Theoperations of 1710 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1710 may beperformed by a configuration manager as described with reference toFIGS. 8 through 11 .

At 1715, the UE may receive DCI associated with a PDSCH transmission forthe SPS configuration. The operations of 1715 may be performed accordingto the methods described herein. In some examples, aspects of theoperations of 1715 may be performed by an SPS manager as described withreference to FIGS. 8 through 11 .

At 1720, the UE may identify, within the DCI, an indication of a set ofTCI states. The operations of 1720 may be performed according to themethods described herein. In some examples, aspects of the operations of1720 may be performed by a TCI state manager as described with referenceto FIGS. 8 through 11 .

At 1725, the UE may receive one or more repetitions of the PDSCHtransmission based on the repetition scheme configuration, or the set ofTCI states, or a combination thereof. The operations of 1725 may beperformed according to the methods described herein. In some examples,aspects of the operations of 1725 may be performed by a PDSCH componentas described with reference to FIGS. 8 through 11 .

FIG. 18 shows a flowchart illustrating a method 1800 that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure. The operations of method 1800may be implemented by a base station 105 or its components as describedherein. For example, the operations of method 1800 may be performed by acommunications manager as described with reference to FIGS. 12 through15 . In some examples, a base station may execute a set of instructionsto control the functional elements of the base station to perform thefunctions described herein. Additionally or alternatively, a basestation may perform aspects of the functions described herein usingspecial-purpose hardware.

At 1805, the base station may transmit, to a UE, a PDSCH configurationand an SPS configuration from a set of one or more SPS configurations.The operations of 1805 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1805may be performed by a configuration component as described withreference to FIGS. 12 through 15 .

At 1810, the base station may transmit, to the UE, DCI associated with aPDSCH transmission for the SPS configuration. The operations of 1810 maybe performed according to the methods described herein. In someexamples, aspects of the operations of 1810 may be performed by a DCIcomponent as described with reference to FIGS. 12 through 15 .

At 1815, the base station may determine, based on a rule, a repetitionnumber for a number of expected instances of the PDSCH transmission,where the rule is based on a priority between a TDRA entry indicated bythe DCI and at least one of the PDSCH configuration or the SPSconfiguration. The operations of 1815 may be performed according to themethods described herein. In some examples, aspects of the operations of1815 may be performed by a repetition configuration manager as describedwith reference to FIGS. 12 through 15 .

At 1820, the base station may transmit, within each SPS time period of aset of SPS time periods, one or more instances of the PDSCH transmissionin accordance with the repetition number. The operations of 1820 may beperformed according to the methods described herein. In some examples,aspects of the operations of 1820 may be performed by an SPStransmission component as described with reference to FIGS. 12 through15 .

FIG. 19 shows a flowchart illustrating a method 1900 that supportstechniques for dynamically aggregating a PDSCH for SPS in accordancewith aspects of the present disclosure. The operations of method 1900may be implemented by a base station 105 or its components as describedherein. For example, the operations of method 1900 may be performed by acommunications manager as described with reference to FIGS. 12 through15 . In some examples, a base station may execute a set of instructionsto control the functional elements of the base station to perform thefunctions described herein. Additionally or alternatively, a basestation may perform aspects of the functions described herein usingspecial-purpose hardware.

At 1905, the base station may transmit, to a UE, an SPS configurationfrom a set of one or more SPS configurations. The operations of 1905 maybe performed according to the methods described herein. In someexamples, aspects of the operations of 1905 may be performed by aconfiguration component as described with reference to FIGS. 12 through15 .

At 1910, the base station may configure a repetition scheme for the UE.The operations of 1910 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1910may be performed by a configuration component as described withreference to FIGS. 12 through 15 .

At 1915, the base station may transmit, to the UE, DCI associated with aPDSCH transmission for the SPS configuration. The operations of 1915 maybe performed according to the methods described herein. In someexamples, aspects of the operations of 1915 may be performed by a DCIcomponent as described with reference to FIGS. 12 through 15 .

At 1920, the base station may configure, within the DCI, an indicationof a set of TCI states. The operations of 1920 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1920 may be performed by a TCI configuration componentas described with reference to FIGS. 12 through 15 .

At 1925, the base station may transmit one or more repetitions of thePDSCH transmission to the UE based on the configured repetition scheme,or the set of TCI states, or a combination thereof. The operations of1925 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1925 may be performed by an SPStransmission component as described with reference to FIGS. 12 through15 .

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communication at a UE, comprising:receiving a physical downlink shared channel configuration and asemi-persistent scheduling configuration from a set of one or moresemi-persistent scheduling configurations; receiving downlink controlinformation associated with a physical downlink shared channeltransmission for the semi-persistent scheduling configuration;determining, based at least in part on a rule, a repetition number for anumber of expected instances of the physical downlink shared channeltransmission, wherein the rule is based at least in part on a prioritybetween a time domain resource allocation entry indicated by thedownlink control information and at least one of the physical downlinkshared channel configuration or the semi-persistent schedulingconfiguration; and receiving, within each semi-persistent schedulingtime period of a plurality of semi-persistent scheduling time periods,one or more instances of the physical downlink shared channeltransmission in accordance with the repetition number.

Aspect 2: The method of aspect 1, wherein determining the repetitionnumber based at least in part on the rule comprises: determining thatthe physical downlink shared channel configuration excludes aconfiguration of a first aggregation factor or the semi-persistentscheduling configuration excludes a configuration of a secondaggregation factor, or a combination thereof.

Aspect 3: The method of any of aspects 1 through 2, wherein determiningthe repetition number based at least in part on the rule comprises:determining that the time domain resource allocation entry indicated bythe downlink control information includes the repetition number; andidentifying a number of repetitions of the physical downlink sharedchannel transmission based at least in part on a value of the repetitionnumber, wherein two or more instances of the physical downlink sharedchannel transmission are received based at least in part on theidentified number of repetitions.

Aspect 4: The method of aspect 3, wherein the number of repetitions ofthe physical downlink shared channel transmission are within a timeperiod that is less than or equal to the semi-persistent scheduling timeperiod.

Aspect 5: The method of any of aspects 1 through 4, wherein determiningthe repetition number based at least in part on the rule comprises:determining that the time domain resource allocation entry indicated bythe downlink control information excludes the repetition number; anddetermining that the number of expected instances of the physicaldownlink shared channel transmission is equal to one based at least inpart on the time domain resource allocation entry excluding therepetition number, wherein a single instance of the physical downlinkshared channel transmission is received based at least in part on thenumber of expected instances.

Aspect 6: The method of any of aspects 1 through 4, wherein determiningthe repetition number based at least in part on the rule comprises:determining that the time domain resource allocation entry indicated bythe downlink control information excludes the repetition number;identifying, based at least in part on the time domain resourceallocation entry excluding the repetition number, a configuration of afirst aggregation factor from the semi-persistent schedulingconfiguration; and identifying a number of repetitions of the physicaldownlink shared channel transmission corresponding to a value of thefirst aggregation factor, wherein two or more instances of the physicaldownlink shared channel transmission are received based at least in parton the identified number of repetitions.

Aspect 7: The method of any of aspects 1 through 4, wherein determiningthe repetition number based at least in part on the rule comprises:determining that the time domain resource allocation entry indicated bythe downlink control information excludes the repetition number;determining, based at least in part on the time domain resourceallocation entry excluding the repetition number, that thesemi-persistent scheduling configuration excludes a configuration of afirst aggregation factor; identifying, based at least in part on thesemi-persistent scheduling configuration excluding the configuration ofthe first aggregation factor, a configuration of a second aggregationfactor from the physical downlink shared channel configuration; andidentifying a number of repetitions of the physical downlink sharedchannel transmission corresponding to a value of the second aggregationfactor, wherein two or more instances of the physical downlink sharedchannel transmission are received based at least in part on theidentified number of repetitions.

Aspect 8: The method of any of aspects 1 through 4, wherein determiningthe repetition number based at least in part on the rule comprises:determining that the time domain resource allocation entry indicated bythe downlink control information excludes the repetition number;determining, based at least in part on the time domain resourceallocation entry excluding the repetition number, that thesemi-persistent scheduling configuration excludes a configuration of afirst aggregation factor; determining, based at least in part on thesemi-persistent scheduling configuration excluding the configuration ofthe first aggregation factor, that the physical downlink shared channelconfiguration excludes a configuration of a second aggregation factor;and determining that the number of expected instances of the physicaldownlink shared channel transmission is equal to one based at least inpart on the time domain resource allocation entry excluding therepetition number, the semi-persistent scheduling configurationexcluding the configuration of the first aggregation factor, and thephysical downlink shared channel configuration excluding theconfiguration of the second aggregation factor, wherein a singleinstance of the physical downlink shared channel transmission isreceived based at least in part on the number of expected instances.

Aspect 9: The method of any of aspects 1 through 8, further comprising:identifying, from the semi-persistent scheduling configuration, aconfiguration of a first aggregation factor; and identifying a number ofrepetitions of the physical downlink shared channel transmissioncorresponding to a value of the first aggregation factor, wherein two ormore instances of the physical downlink shared channel transmission arereceived based at least in part on the identified number of repetitions.

Aspect 10: The method of any of aspects 1 through 9, further comprising:determining that the semi-persistent scheduling configuration excludes aconfiguration of a first aggregation factor; identifying, based at leastin part on the semi-persistent scheduling configuration excluding theconfiguration of the first aggregation factor, a configuration of asecond aggregation factor from the physical downlink shared channelconfiguration; and identifying a number of repetitions of the physicaldownlink shared channel transmission corresponding to a value of thesecond aggregation factor, wherein two or more instances of the physicaldownlink shared channel transmission are received based at least in parton the identified number of repetitions.

Aspect 11: The method of any of aspects 1 through 10, furthercomprising: determining that the semi-persistent schedulingconfiguration excludes a configuration of a first aggregation factor;determining, based at least in part on the semi-persistent schedulingconfiguration excluding the configuration of the first aggregationfactor, that the physical downlink shared channel configuration excludesa configuration of a second aggregation factor; and determining that thenumber of expected instances of the physical downlink shared channeltransmission is equal to one based at least in part on thesemi-persistent scheduling configuration excluding the configuration ofthe first aggregation factor and the physical downlink shared channelconfiguration excluding the configuration of the second aggregationfactor, wherein a single instance of the physical downlink sharedchannel transmission is received based at least in part on the number ofexpected instances.

Aspect 12: The method of any of aspects 1 through 11, furthercomprising: identifying, from the physical downlink shared channelconfiguration, a configuration of a first aggregation factor; andidentifying a number of repetitions of the physical downlink sharedchannel transmission corresponding to a value of the first aggregationfactor, wherein two or more instances of the physical downlink sharedchannel transmission are received based at least in part on theidentified number of repetitions.

Aspect 13: The method of any of aspects 1 through 12, furthercomprising: determining that the number of expected instances of thephysical downlink shared channel transmission is equal to one based atleast in part on the physical downlink shared channel configurationexcluding a configuration of a first aggregation factor, wherein asingle instance of the physical downlink shared channel transmission isreceived based at least in part on the number of expected instances.

Aspect 14: The method of any of aspects 1 through 13, furthercomprising: receiving a configuration of the time domain resourceallocation table via radio resource control signaling, wherein the timedomain resource allocation table comprises a plurality of time domainresource allocation entries, and wherein at least one time domainresource allocation entry of the plurality of time domain resourceallocation entries includes the repetition number indicated by at leastone column of the time domain resource allocation table.

Aspect 15: The method of any of aspects 1 through 14, wherein thedownlink control information has a cyclic redundancy check that isscrambled by a configured scheduling radio network temporary identifier,the downlink control information comprising a new data indicator equalto zero, and the downlink control information activates thesemi-persistent scheduling configuration.

Aspect 16: The method of any of aspects 1 through 14, wherein thedownlink control information has a cyclic redundancy check that isscrambled by a configured scheduling radio network temporary identifier,the downlink control information comprising a new data indicator equalto one, and the physical downlink shared channel transmission comprisesa retransmission of semi-persistently scheduled physical downlink sharedchannel scheduled by the downlink control information.

Aspect 17: The method of any of aspects 1 through 16, wherein the one ormore instances of the physical downlink shared channel transmission arereceived in a different slot time period of a plurality of consecutiveslot time periods.

Aspect 18: The method of any of aspects 1 through 17, wherein thedownlink control information has a downlink control information format1_1 or 1_2.

Aspect 19: The method of any of aspects 1 through 18, wherein thephysical downlink shared channel configuration and the semi-persistentscheduling configuration are received via radio resource controlsignaling.

Aspect 20: A method for wireless communication at a UE, comprising:receiving a semi-persistent scheduling configuration from a set of oneor more semi-persistent scheduling configurations; identifying arepetition scheme configuration; receiving downlink control informationassociated with a physical downlink shared channel transmission for thesemi-persistent scheduling configuration; identifying, within thedownlink control information, an indication of a plurality oftransmission configuration indicator states; and receiving one or morerepetitions of the physical downlink shared channel transmission basedat least in part on the repetition scheme configuration, or theplurality of transmission configuration indicator states, or acombination thereof.

Aspect 21: The method of aspect 20, further comprising: identifying anumber of the one or more repetitions of a physical downlink sharedchannel based at least in part on the physical downlink shared channelexcluding a configuration of a first aggregation factor or thesemi-persistent scheduling configuration excluding a configuration of asecond aggregation factor, or a combination thereof.

Aspect 22: The method of any of aspects 20 through 21, wherein receivingthe one or more repetitions of the physical downlink shared channeltransmission comprises: receiving the one or more repetitions of thephysical downlink shared channel transmission within a same slot timeperiod, the slot time period occurring within each semi-persistentscheduling time period of a plurality of semi-persistent scheduling timeperiods.

Aspect 23: The method of any of aspects 20 through 21, wherein receivingthe one or more repetitions of the physical downlink shared channeltransmission comprises: receiving the one or more repetitions of thephysical downlink shared channel transmission within a plurality ofconsecutive slot time periods occurring within each semi-persistentscheduling time period of a plurality of semi-persistent scheduling timeperiods, each slot time period of the plurality of consecutive slot timeperiods comprising two repetitions of the physical downlink sharedchannel transmission.

Aspect 24: The method of aspect 23, further comprising: identifying,from the semi-persistent scheduling configuration, a configuration of afirst aggregation factor; and identifying a number of the plurality ofconsecutive slot time periods that corresponds to a value of the firstaggregation factor.

Aspect 25: The method of any of aspects 23 through 24, furthercomprising: receiving a physical downlink shared channel configuration;determining that the semi-persistent scheduling configuration excludes aconfiguration of a first aggregation factor; identifying, based at leastin part on the semi-persistent scheduling configuration excluding theconfiguration of the first aggregation factor, a configuration of asecond aggregation factor from the physical downlink shared channelconfiguration; and identifying a number of the plurality of consecutiveslot time periods that corresponds to a value of the second aggregationfactor.

Aspect 26: The method of any of aspects 20 through 25, whereinidentifying the repetition scheme configuration comprises: receiving aphysical downlink shared channel configuration; and identifying therepetition scheme configuration based at least in part on the receivedphysical downlink shared channel configuration, wherein thesemi-persistent scheduling configuration excludes the repetition schemeconfiguration.

Aspect 27: The method of any of aspects 20 through 26, wherein theplurality of transmission configuration indicator states comprises twotransmission configuration indicator states.

Aspect 28: The method of any of aspects 20 through 27, wherein therepetition scheme configuration is from a group consisting of a firstfrequency division multiplexing scheme, a second frequency divisionmultiplexing scheme, and a time division multiplexing scheme.

Aspect 29: The method of any of aspects 20 through 28, wherein thedownlink control information has a cyclic redundancy check that isscrambled by a configured scheduling radio network temporary identifier,the downlink control information comprising a new data indicator equalto zero, and the downlink control information activates thesemi-persistent scheduling configuration.

Aspect 30: The method of any of aspects 20 through 29, whereinidentifying the repetition scheme configuration comprises: identifyingthe repetition scheme configuration based at least in part on thereceived semi-persistent scheduling configuration.

Aspect 31: A method for wireless communication at a base station,comprising: transmitting, to a UE, a physical downlink shared channelconfiguration and a semi-persistent scheduling configuration from a setof one or more semi-persistent scheduling configurations; transmitting,to the UE, downlink control information associated with a physicaldownlink shared channel transmission for the semi-persistent schedulingconfiguration; determining, based at least in part on a rule, arepetition number for a number of expected instances of the physicaldownlink shared channel transmission, wherein the rule is based at leastin part on a priority between a time domain resource allocation entryindicated by the downlink control information and at least one of thephysical downlink shared channel configuration or the semi-persistentscheduling configuration; and transmitting, within each semi-persistentscheduling time period of a plurality of semi-persistent scheduling timeperiods, one or more instances of the physical downlink shared channeltransmission in accordance with the repetition number.

Aspect 32: The method of aspect 31, wherein determining the repetitionnumber based at least in part on the rule comprises: determining thatthe time domain resource allocation entry indicated by the downlinkcontrol information includes the repetition number; and identifying anumber of repetitions of the physical downlink shared channeltransmission based at least in part on a value of the repetition number,wherein two or more instances of the physical downlink shared channeltransmission are transmitted based at least in part on the identifiednumber of repetitions.

Aspect 33: The method of any of aspects 31 through 32, wherein thenumber of repetitions of the physical downlink shared channeltransmission are within a time period that is less than or equal to thesemi-persistent scheduling time period.

Aspect 34: The method of aspect 31, wherein determining the repetitionnumber based at least in part on the rule comprises: determining thatthe time domain resource allocation entry indicated by the downlinkcontrol information excludes the repetition number; and determining thatthe number of expected instances of the physical downlink shared channeltransmission is equal to one based at least in part on the time domainresource allocation entry excluding the repetition number, wherein asingle instance of the physical downlink shared channel transmission istransmitted based at least in part on the number of expected instances.

Aspect 35: The method of aspect 31, wherein determining the repetitionnumber based at least in part on the rule comprises: determining thatthe time domain resource allocation entry indicated by the downlinkcontrol information excludes the repetition number, wherein thesemi-persistent scheduling configuration comprises a configuration of afirst aggregation factor; and identifying a number of repetitions of thephysical downlink shared channel transmission corresponding to a valueof the first aggregation factor, wherein two or more instances of thephysical downlink shared channel transmission are transmitted based atleast in part on the identified number of repetitions.

Aspect 36: The method of aspect 31, wherein determining the repetitionnumber based at least in part on the rule comprises: determining thatthe time domain resource allocation entry indicated by the downlinkcontrol information excludes the repetition number, wherein thesemi-persistent scheduling configuration excludes a configuration of afirst aggregation factor and the physical downlink shared channelconfiguration comprises a configuration of a second aggregation factor;and identifying a number of repetitions of the physical downlink sharedchannel transmission corresponding to a value of the second aggregationfactor, wherein two or more instances of the physical downlink sharedchannel transmission are transmitted based at least in part on theidentified number of repetitions.

Aspect 37: The method of aspect 31, wherein determining the repetitionnumber based at least in part on the rule comprises: determining thatthe time domain resource allocation entry indicated by the downlinkcontrol information excludes the repetition number, wherein thesemi-persistent scheduling configuration excludes a configuration of afirst aggregation factor and the physical downlink shared channelconfiguration excludes a configuration of a second aggregation factor;and determining that the number of expected instances of the physicaldownlink shared channel transmission is equal to one based at least inpart on the time domain resource allocation entry excluding therepetition number, the semi-persistent scheduling configurationexcluding a configuration of the first aggregation factor, and thephysical downlink shared channel configuration excluding a configurationof the second aggregation factor, wherein a single instance of thephysical downlink shared channel transmission is transmitted based atleast in part on the number of expected instances.

Aspect 38: The method of aspect 31, wherein determining the repetitionnumber based at least in part on the rule comprises: configuring a firstaggregation factor as part of the semi-persistent schedulingconfiguration; and identifying a number of repetitions of the physicaldownlink shared channel transmission corresponding to a value of thefirst aggregation factor, wherein two or more instances of the physicaldownlink shared channel transmission are transmitted based at least inpart on the identified number of repetitions.

Aspect 39: The method of aspect 31, wherein determining the repetitionnumber based at least in part on the rule comprises: determining thatthe semi-persistent scheduling configuration excludes a configuration ofa first aggregation factor, wherein the physical downlink shared channelconfiguration comprises a configuration of a second aggregation factor;and identifying a number of repetitions of the physical downlink sharedchannel transmission corresponding to a value of the second aggregationfactor, wherein two or more instances of the physical downlink sharedchannel transmission are transmitted based at least in part on theidentified number of repetitions.

Aspect 40: The method of aspect 31, wherein determining the repetitionnumber based at least in part on the rule comprises: determining thatthe number of expected instances of the physical downlink shared channeltransmission is equal to one based at least in part on thesemi-persistent scheduling configuration excluding a configuration of afirst aggregation factor and the physical downlink shared channelconfiguration excluding a configuration of a second aggregation factor,wherein a single instance of the physical downlink shared channeltransmission is transmitted based at least in part on the number ofexpected instances.

Aspect 41: The method of aspect 31, wherein determining the repetitionnumber based at least in part on the rule comprises: configuring a firstaggregation factor as part of the physical downlink shared channelconfiguration; and identifying a number of repetitions of the physicaldownlink shared channel transmission corresponding to a value of thefirst aggregation factor, wherein two or more instances of the physicaldownlink shared channel transmission are transmitted based at least inpart on the identified number of repetitions.

Aspect 42: The method of aspect 31, wherein determining the repetitionnumber based at least in part on the rule comprises: determining thatthe number of expected instances of the physical downlink shared channeltransmission is equal to one based at least in part on the physicaldownlink shared channel configuration excluding a configuration of afirst aggregation factor, wherein a single instance of the physicaldownlink shared channel transmission is transmitted based at least inpart on the number of expected instances.

Aspect 43: The method of any of aspects 31 through 42, wherein the timedomain resource allocation entry is an entry from a time domain resourceallocation table that comprises a plurality of time domain resourceallocation entries, and at least one time domain resource allocationentry of the plurality of time domain resource allocation entriesincludes the repetition number.

Aspect 44: The method of aspect 43, further comprising: transmitting, tothe UE, a configuration of the time domain resource allocation table viaradio resource control signaling.

Aspect 45: The method of any of aspects 43 through 44, wherein therepetition number is indicated by at least one column of the time domainresource allocation table.

Aspect 46: The method of any of aspects 31 through 45, wherein thedownlink control information comprises a new data indicator equal tozero, and the downlink control information activates the semi-persistentscheduling configuration.

Aspect 47: The method of any of aspects 31 through 46, wherein thedownlink control information comprises a new data indicator equal toone, and the physical downlink shared channel transmission comprises aretransmission of semi-persistently scheduled physical downlink sharedchannel scheduled by the downlink control information.

Aspect 48: The method of any of aspects 31 through 47, wherein the oneor more instances of the physical downlink shared channel transmissionare received in a different slot time period of a plurality ofconsecutive slot time periods.

Aspect 49: The method of any of aspects 31 through 48, wherein thedownlink control information has a downlink control information format1_1.

Aspect 50: The method of any of aspects 31 through 49, wherein thedownlink control information has a downlink control information format1_2.

Aspect 51: The method of any of aspects 31 through 50, whereindetermining the repetition number based at least in part on the rulecomprises: determining that the physical downlink shared channelconfiguration excludes a configuration of a first aggregation factor orthe semi-persistent scheduling configuration excludes a configuration ofa second aggregation factor, or both.

Aspect 52: A method for wireless communication at a base station,comprising: transmitting, to a UE, a semi-persistent schedulingconfiguration from a set of one or more semi-persistent schedulingconfigurations; configuring a repetition scheme for the UE;transmitting, to the UE, downlink control information associated with aphysical downlink shared channel transmission for the semi-persistentscheduling configuration; configuring, within the downlink controlinformation, an indication of a plurality of transmission configurationindicator states; and transmitting one or more repetitions of thephysical downlink shared channel transmission to the UE based at leastin part on the configured repetition scheme, or the plurality oftransmission configuration indicator states, or a combination thereof.

Aspect 53: The method of aspect 52, wherein transmitting the one or morerepetitions of the physical downlink shared channel transmissioncomprises: transmitting the one or more repetitions of the physicaldownlink shared channel transmission within a same slot time period, theslot time period occurring within each semi-persistent scheduling timeperiod of a plurality of semi-persistent scheduling time periods.

Aspect 54: The method of any of aspects 52 through 53, whereintransmitting the one or more repetitions of the physical downlink sharedchannel transmission comprises: transmitting the one or more repetitionsof the physical downlink shared channel transmission within a pluralityof consecutive slot time periods occurring within each semi-persistentscheduling time period of a plurality of semi-persistent scheduling timeperiods, each slot time period of the plurality of consecutive slot timeperiods comprising two repetitions of the physical downlink sharedchannel transmission.

Aspect 55: The method of aspect 54, further comprising: configuring afirst aggregation factor as part of the semi-persistent schedulingconfiguration, wherein a number of the plurality of consecutive slottime periods corresponds to a value of the first aggregation factor.

Aspect 56: The method of any of aspects 54 through 55, furthercomprising: configuring, based at least in part on the semi-persistentscheduling configuration excluding a configuration of a firstaggregation factor, a second aggregation factor as part of a physicaldownlink shared channel configuration; and transmitting the physicaldownlink shared channel configuration to the UE, wherein a number of theplurality of consecutive slot time periods corresponds to a value of thesecond aggregation factor.

Aspect 57: The method of any of aspects 52 through 56, furthercomprising: transmitting an indication of the configured repetitionscheme as part of the semi-persistent scheduling configuration.

Aspect 58: The method of any of aspects 52 through 57, furthercomprising: transmitting, to the UE, a physical downlink shared channelconfiguration comprising an indication of the configured repetitionscheme, wherein the semi-persistent scheduling configuration excludesthe indication of the configured repetition scheme.

Aspect 59: The method of any of aspects 52 through 58, wherein theplurality of transmission configuration indicator states comprises twotransmission configuration indicator states.

Aspect 60: The method of any of aspects 52 through 59, wherein theconfigured repetition scheme is from the group consisting of a firstfrequency division multiplexing scheme, a second frequency divisionmultiplexing scheme, and a time division multiplexing scheme.

Aspect 61: The method of any of aspects 52 through 60, wherein thedownlink control information has a cyclic redundancy check that isscrambled by a configured scheduling radio network temporary identifier,the downlink control information comprising a new data indicator equalto zero, and the downlink control information activates thesemi-persistent scheduling configuration.

Aspect 62: The method of any of aspects 52 through 61, furthercomprising: identifying a number of the one or more repetitions of aphysical downlink shared channel based at least in part on the physicaldownlink shared channel excluding a configuration of a first aggregationfactor or the semi-persistent scheduling configuration excluding aconfiguration of a second aggregation factor, or both.

Aspect 63: An apparatus for wireless communication at a UE, comprising aprocessor; memory coupled with the processor; and instructions stored inthe memory and executable by the processor to cause the apparatus toperform a method of any of aspects 1 through 19.

Aspect 64: An apparatus for wireless communication at a UE, comprisingat least one means for performing a method of any of aspects 1 through19.

Aspect 65: A non-transitory computer-readable medium storing code forwireless communication at a UE, the code comprising instructionsexecutable by a processor to perform a method of any of aspects 1through 19.

Aspect 66: An apparatus for wireless communication at a UE, comprising aprocessor; memory coupled with the processor; and instructions stored inthe memory and executable by the processor to cause the apparatus toperform a method of any of aspects 20 through 30.

Aspect 67: An apparatus for wireless communication at a UE, comprisingat least one means for performing a method of any of aspects 20 through30.

Aspect 68: A non-transitory computer-readable medium storing code forwireless communication at a UE, the code comprising instructionsexecutable by a processor to perform a method of any of aspects 20through 30.

Aspect 69: An apparatus for wireless communication at a base station,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform a method of any of aspects 31 through 51.

Aspect 70: An apparatus for wireless communication at a base station,comprising at least one means for performing a method of any of aspects31 through 51.

Aspect 71: A non-transitory computer-readable medium storing code forwireless communication at a base station, the code comprisinginstructions executable by a processor to perform a method of any ofaspects 31 through 51.

Aspect 72: An apparatus for wireless communication at a base station,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform a method of any of aspects 52 through 62.

Aspect 73: An apparatus for wireless communication at a base station,comprising at least one means for performing a method of any of aspects52 through 62.

Aspect 74: A non-transitory computer-readable medium storing code forwireless communication at a base station, the code comprisinginstructions executable by a processor to perform a method of any ofaspects 52 through 62.

It should be noted that the methods described herein describe possibleimplementations, and that the operations and the steps may be rearrangedor otherwise modified and that other implementations are possible.Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may bedescribed for purposes of example, and LTE, LTE-A, LTE-A Pro, or NRterminology may be used in much of the description, the techniquesdescribed herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NRnetworks. For example, the described techniques may be applicable tovarious other wireless communications systems such as Ultra MobileBroadband (UMB), Institute of Electrical and Electronics Engineers(IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, aswell as other systems and radio technologies not explicitly mentionedherein.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connectionwith the disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, a CPU, an FPGA or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but in the alternative, the processor may be anyprocessor, controller, microcontroller, or state machine. A processormay also be implemented as a combination of computing devices (e.g., acombination of a DSP and a microprocessor, multiple microprocessors, oneor more microprocessors in conjunction with a DSP core, or any othersuch configuration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described herein may be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations.

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that may beaccessed by a general-purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media mayinclude RAM, ROM, electrically erasable programmable ROM (EEPROM), flashmemory, compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that may be used to carry or store desired programcode means in the form of instructions or data structures and that maybe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of computer-readable medium. Disk and disc,as used herein, include CD, laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations herein are also included within the scope ofcomputer-readable media.

As used herein, including in the claims, “or” as used in a list of items(e.g., a list of items prefaced by a phrase such as “at least one of” or“one or more of”) indicates an inclusive list such that, for example, alist of at least one of A, B, or C means A or B or C or AB or AC or BCor ABC (i.e., A and B and C). Also, as used herein, the phrase “basedon” shall not be construed as a reference to a closed set of conditions.For example, an example step that is described as “based on condition A”may be based on both a condition A and a condition B without departingfrom the scope of the present disclosure. In other words, as usedherein, the phrase “based on” shall be construed in the same manner asthe phrase “based at least in part on.”

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label, or othersubsequent reference label.

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “example” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, known structures and devices are shown inblock diagram form in order to avoid obscuring the concepts of thedescribed examples.

The description herein is provided to enable a person having ordinaryskill in the art to make or use the disclosure. Various modifications tothe disclosure will be apparent to a person having ordinary skill in theart, and the generic principles defined herein may be applied to othervariations without departing from the scope of the disclosure. Thus, thedisclosure is not limited to the examples and designs described herein,but is to be accorded the broadest scope consistent with the principlesand novel features disclosed herein.

What is claimed is:
 1. A method for wireless communication at a userequipment (UE), comprising: receiving a physical downlink shared channelconfiguration and a semi-persistent scheduling configuration from a setof one or more semi-persistent scheduling configurations; receivingdownlink control information associated with a physical downlink sharedchannel transmission for the semi-persistent scheduling configuration;determining, based at least in part on a rule, a repetition number for anumber of expected instances of the physical downlink shared channeltransmission, wherein the rule is based at least in part on a prioritybetween a time domain resource allocation entry indicated by thedownlink control information and at least one of the physical downlinkshared channel configuration or the semi-persistent schedulingconfiguration; and receiving, within each semi-persistent schedulingtime period of a plurality of semi-persistent scheduling time periods,one or more instances of the physical downlink shared channeltransmission in accordance with the repetition number.
 2. The method ofclaim 1, wherein determining the repetition number based at least inpart on the rule comprises: determining that the physical downlinkshared channel configuration excludes a configuration of a firstaggregation factor or that the semi-persistent scheduling configurationexcludes a configuration of a second aggregation factor, or acombination thereof.
 3. The method of claim 1, wherein determining therepetition number based at least in part on the rule comprises:determining that the time domain resource allocation entry indicated bythe downlink control information includes the repetition number; andidentifying a number of repetitions of the physical downlink sharedchannel transmission based at least in part on a value of the repetitionnumber, wherein two or more instances of the physical downlink sharedchannel transmission are received based at least in part on theidentified number of repetitions.
 4. The method of claim 3, wherein thenumber of repetitions of the physical downlink shared channeltransmission are within a time period that is less than or equal to asemi-persistent scheduling time period of the plurality ofsemi-persistent scheduling time periods.
 5. The method of claim 1,wherein determining the repetition number based at least in part on therule comprises: determining that the time domain resource allocationentry indicated by the downlink control information excludes therepetition number; and determining that the number of expected instancesof the physical downlink shared channel transmission is equal to onebased at least in part on the time domain resource allocation entryexcluding the repetition number, wherein a single instance of thephysical downlink shared channel transmission is received based at leastin part on the number of expected instances.
 6. The method of claim 1,wherein determining the repetition number based at least in part on therule comprises: determining that the time domain resource allocationentry indicated by the downlink control information excludes therepetition number; identifying, based at least in part on the timedomain resource allocation entry excluding the repetition number, aconfiguration of a first aggregation factor from the semi-persistentscheduling configuration; and identifying a number of repetitions of thephysical downlink shared channel transmission corresponding to a valueof the first aggregation factor, wherein two or more instances of thephysical downlink shared channel transmission are received based atleast in part on the identified number of repetitions.
 7. The method ofclaim 1, wherein determining the repetition number based at least inpart on the rule comprises: determining that the time domain resourceallocation entry indicated by the downlink control information excludesthe repetition number; determining, based at least in part on the timedomain resource allocation entry excluding the repetition number, thatthe semi-persistent scheduling configuration excludes a configuration ofa first aggregation factor; identifying, based at least in part on thesemi-persistent scheduling configuration excluding the configuration ofthe first aggregation factor, a configuration of a second aggregationfactor from the physical downlink shared channel configuration; andidentifying a number of repetitions of the physical downlink sharedchannel transmission corresponding to a value of the second aggregationfactor, wherein two or more instances of the physical downlink sharedchannel transmission are received based at least in part on theidentified number of repetitions.
 8. The method of claim 1, whereindetermining the repetition number based at least in part on the rulecomprises: determining that the time domain resource allocation entryindicated by the downlink control information excludes the repetitionnumber; determining, based at least in part on the time domain resourceallocation entry excluding the repetition number, that thesemi-persistent scheduling configuration excludes a configuration of afirst aggregation factor; determining, based at least in part on thesemi-persistent scheduling configuration excluding the configuration ofthe first aggregation factor, that the physical downlink shared channelconfiguration excludes a configuration of a second aggregation factor;and determining that the number of expected instances of the physicaldownlink shared channel transmission is equal to one based at least inpart on the time domain resource allocation entry excluding therepetition number, the semi-persistent scheduling configurationexcluding the configuration of the first aggregation factor, and thephysical downlink shared channel configuration excluding theconfiguration of the second aggregation factor, wherein a singleinstance of the physical downlink shared channel transmission isreceived based at least in part on the number of expected instances. 9.The method of claim 1, further comprising: identifying, from thesemi-persistent scheduling configuration, a configuration of a firstaggregation factor; and identifying a number of repetitions of thephysical downlink shared channel transmission corresponding to a valueof the first aggregation factor, wherein two or more instances of thephysical downlink shared channel transmission are received based atleast in part on the identified number of repetitions.
 10. The method ofclaim 1, further comprising: determining that the semi-persistentscheduling configuration excludes a configuration of a first aggregationfactor; identifying, based at least in part on the semi-persistentscheduling configuration excluding the configuration of the firstaggregation factor, a configuration of a second aggregation factor fromthe physical downlink shared channel configuration; and identifying anumber of repetitions of the physical downlink shared channeltransmission corresponding to a value of the second aggregation factor,wherein two or more instances of the physical downlink shared channeltransmission are received based at least in part on the identifiednumber of repetitions.
 11. The method of claim 1, further comprising:determining that the semi-persistent scheduling configuration excludes aconfiguration of a first aggregation factor; determining, based at leastin part on the semi-persistent scheduling configuration excluding theconfiguration of the first aggregation factor, that the physicaldownlink shared channel configuration excludes a configuration of asecond aggregation factor; and determining that the number of expectedinstances of the physical downlink shared channel transmission is equalto one based at least in part on the semi-persistent schedulingconfiguration excluding the configuration of the first aggregationfactor and the physical downlink shared channel configuration excludingthe configuration of the second aggregation factor, wherein a singleinstance of the physical downlink shared channel transmission isreceived based at least in part on the number of expected instances. 12.The method of claim 1, further comprising: identifying, from thephysical downlink shared channel configuration, a configuration of afirst aggregation factor; and identifying a number of repetitions of thephysical downlink shared channel transmission corresponding to a valueof the first aggregation factor, wherein two or more instances of thephysical downlink shared channel transmission are received based atleast in part on the identified number of repetitions.
 13. The method ofclaim 1, further comprising: determining that the number of expectedinstances of the physical downlink shared channel transmission is equalto one based at least in part on the physical downlink shared channelconfiguration excluding a configuration of a first aggregation factor,wherein a single instance of the physical downlink shared channeltransmission is received based at least in part on the number ofexpected instances.
 14. The method of claim 1, further comprising:receiving a configuration of a time domain resource allocation table viaradio resource control signaling, wherein the time domain resourceallocation table comprises a plurality of time domain resourceallocation entries, and wherein at least one time domain resourceallocation entry of the plurality of time domain resource allocationentries includes the repetition number indicated by at least one columnof the time domain resource allocation table.
 15. The method of claim 1,wherein the downlink control information has a cyclic redundancy checkthat is scrambled by a configured scheduling radio network temporaryidentifier, the downlink control information comprising a new dataindicator equal to zero, and wherein the downlink control informationactivates the semi-persistent scheduling configuration.
 16. The methodof claim 1, wherein the downlink control information has a cyclicredundancy check that is scrambled by a configured scheduling radionetwork temporary identifier, the downlink control informationcomprising a new data indicator equal to one, and wherein the physicaldownlink shared channel transmission comprises a retransmission ofsemi-persistently scheduled physical downlink shared channel scheduledby the downlink control information.
 17. The method of claim 1, whereinthe one or more instances of the physical downlink shared channeltransmission are received in a different slot time period of a pluralityof consecutive slot time periods.
 18. The method of claim 1, wherein thedownlink control information has a downlink control information format1_1 or 1_2.
 19. A method for wireless communication at a user equipment(UE), comprising: receiving a semi-persistent scheduling configurationfrom a set of one or more semi-persistent scheduling configurations;identifying a repetition scheme configuration; receiving downlinkcontrol information associated with a physical downlink shared channeltransmission for the semi-persistent scheduling configuration;identifying, within the downlink control information, an indication of aplurality of transmission configuration indicator states; and receivingone or more repetitions of the physical downlink shared channeltransmission based at least in part on the repetition schemeconfiguration and the plurality of transmission configuration indicatorstates, the one or more repetitions corresponding to respectivetransmission occasions having non-overlapping time domain resourceallocations within a same slot time period.
 20. The method of claim 19,further comprising: identifying a number of the one or more repetitionsof a physical downlink shared channel based at least in part on thephysical downlink shared channel excluding a configuration of a firstaggregation factor or the semi-persistent scheduling configurationexcluding a configuration of a second aggregation factor, or acombination thereof.
 21. The method of claim 19, wherein the same slottime period occurs within each semi-persistent scheduling time period ofa plurality of semi-persistent scheduling time periods.
 22. The methodof claim 19, wherein receiving the one or more repetitions of thephysical downlink shared channel transmission comprises: receiving theone or more repetitions of the physical downlink shared channeltransmission within a plurality of consecutive slot time periodsoccurring within each semi-persistent scheduling time period of aplurality of semi-persistent scheduling time periods, each slot timeperiod of the plurality of consecutive slot time periods comprising tworepetitions of the physical downlink shared channel transmission. 23.The method of claim 22, further comprising: identifying, from thesemi-persistent scheduling configuration, a configuration of a firstaggregation factor; and identifying a number of the plurality ofconsecutive slot time periods that corresponds to a value of the firstaggregation factor.
 24. The method of claim 22, further comprising:receiving a physical downlink shared channel configuration; determiningthat the semi-persistent scheduling configuration excludes aconfiguration of a first aggregation factor; identifying, based at leastin part on the semi-persistent scheduling configuration excluding theconfiguration of the first aggregation factor, a configuration of asecond aggregation factor from the physical downlink shared channelconfiguration; and identifying a number of the plurality of consecutiveslot time periods that corresponds to a value of the second aggregationfactor.
 25. The method of claim 19, wherein identifying the repetitionscheme configuration comprises: receiving a physical downlink sharedchannel configuration; and identifying the repetition schemeconfiguration based at least in part on the received physical downlinkshared channel configuration, wherein the semi-persistent schedulingconfiguration excludes the repetition scheme configuration.
 26. Themethod of claim 19, wherein the plurality of transmission configurationindicator states comprises two transmission configuration indicatorstates.
 27. The method of claim 19, wherein the repetition schemeconfiguration comprises a time division multiplexing scheme.
 28. Themethod of claim 19, wherein the downlink control information has acyclic redundancy check that is scrambled by a configured schedulingradio network temporary identifier, the downlink control informationcomprising a new data indicator equal to zero, and wherein the downlinkcontrol information activates the semi-persistent schedulingconfiguration.
 29. An apparatus for wireless communication, comprising:a processor, memory coupled with the processor; and instructions storedin the memory and executable by the processor to cause the apparatus to:receive a physical downlink shared channel configuration and asemi-persistent scheduling configuration from a set of one or moresemi-persistent scheduling configurations; receive downlink controlinformation associated with a physical downlink shared channeltransmission for the semi-persistent scheduling configuration;determine, based at least in part on a rule, a repetition number for anumber of expected instances of the physical downlink shared channeltransmission, wherein the rule is based at least in part on a prioritybetween a time domain resource allocation entry indicated by thedownlink control information and at least one of the physical downlinkshared channel configuration or the semi-persistent schedulingconfiguration; and receive, within each semi-persistent scheduling timeperiod of a plurality of semi-persistent scheduling time periods, one ormore instances of the physical downlink shared channel transmission inaccordance with the repetition number.
 30. An apparatus for wirelesscommunication, comprising: a processor, memory coupled with theprocessor; and instructions stored in the memory and executable by theprocessor to cause the apparatus to: receive a semi-persistentscheduling configuration from a set of one or more semi-persistentscheduling configurations; identify a repetition scheme configuration;receive downlink control information associated with a physical downlinkshared channel transmission for the semi-persistent schedulingconfiguration; identify, within the downlink control information, anindication of a plurality of transmission configuration indicatorstates; and receive one or more repetitions of the physical downlinkshared channel transmission based at least in part on the repetitionscheme configuration and the plurality of transmission configurationindicator states, the one or more repetitions corresponding torespective transmission occasions having non-overlapping time domainresource allocations within a same slot time period.